Kubernetes: Crossing the Chasm
summary
Kubernetes reaches mainstream adoption but brings concrete pains and wins: an initial Beijing–Singapore Federation design collapses after a Federation deprecation, a German bank runs one non‑prod DC plus four production clusters to balance isolation and cost, GitOps becomes the chosen method for strong audits and approvals (GitOps as access control), Ericsson ships apps as Helm charts to customers, and migrations fail when teams lack tests, reproducible dev environments and automation.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:52Crossing the Chasm
- 6:03Diffusion of Innovation
- 11:53How Many Clusters Do I Need
- 14:37Run a Cluster across Multiple Regions
- 14:59Scale
- 19:53Erickson
- 30:01Stateful Applications
related talks
42mMastering Kubernetes: Challenges, Strategies, and Best Practices
19mThe Path to Kubernetes Adoption Is (Not Just) Installing Kubernetes
29m11 5 years of kubernetes and looking to the future
35mNavigating the Kubernetes Odyssey: Lessons from Early Adoption and Sustained...
19mPains and gains of Kubernetes for Developers, story from experience
40mThe Good, the Bad, and the Ugly of Managing Production Systems with Kubernetes
51mKubernetes for the Impatient
29mTales from the Branches: GitOps in the Real World