Kubernetes for the konfused, a strategy toolkit for normals
summary
Practical checklist for deciding whether to adopt Kubernetes: map where workloads run (public cloud vs private cloud, BYO Kubernetes vs managed services like GKE/EKS/AKS), list missing platform pieces (persistent storage, networking, image registry, service backing), decide who operates the cluster and whether to adopt an SRE/platform approach or keep old ticket-driven ops, choose initial projects — pick small real apps rather than one giant legacy lift — and plan app changes (12‑factor, microservices, CI/CD) plus measurable business outcomes.
AI-written summary · about
chapters (14)
- 0:00Managing container clusters
- 2:59How Kubernetes works
- 5:25Strategic planning goals
- 7:15Operations and culture
- 10:30Industry adoption metrics
- 12:20Focusing on user outcomes
- 14:03Adoption and architecture
- 18:57Modernizing operations
- 23:54Cloud-native application design
- 28:53Selecting initial projects
- 33:22Handling legacy systems
- 35:11Choosing a platform model
- 41:27Emerging trends: Serverless
- 46:18Conclusion and Q&A
related talks
39mKubernetes is awesome – but …
47mDo We Really Need Kubernetes? A Tactical Guide to Cloud Native
36mKubernetes, Decisions
46mWhat I wish I knew about Kubernetes bef…
51mKubernetes for the Impatient
14mLessons from the Kubernetes Adventure
32mLaying the Foundation: Real World Kubernetes Deployment Patterns
19mKube Me This! Kubernetes Ideas and Best Practices