The Journey of Adidas to a Global Kubernetes Rollout
summary
Adidas selects Kubernetes with Giant Swarm as the platform and migrates beginning 2015 toward globally distributed microservices, running dozens of clusters across clouds and on-prem datacenters to support peak end‑of‑year sales. The build centers on multi-tenant clusters, Prometheus-based monitoring and a central control plane that performs automated cluster upgrades and namespace isolation (about 25 namespaces per cluster reported). Organizational shifts and tooling for upgrades and observability prove critical and production traffic succeeds during holiday sales.
AI-written summary · about
chapters (7)
- 0:00Adidas platform journey
- 6:47From hosting to Kubernetes
- 10:17Cross-cloud Kubernetes rollout
- 19:34Production scaling challenges
- 25:31Multi-tenant cluster configs
- 29:25Monitoring large-scale Kubernetes
- 33:21Learnings and future outlook
related talks
24mReady to Go - Measuring Release Fitness at Scale
35mKubernetes journey
25mThe Cloud Native Journey at Adobe
19mBuilding an On-Premise Kubernetes...
19mPains and gains of Kubernetes for Developers, story from experience
46mKeep Building Fresh: Shopify's Journey to Kubernetes
35mTo Infinite Scale and Beyond: Operating Kubernetes Past the Steady State
33mKubernetes: Crossing the Chasm