Do We Really Need Kubernetes? A Tactical Guide to Cloud Native
summary
Explains a practical decision framework: five questions (scope, architecture, scalability, team skill, who runs it) and concrete tradeoffs — when Kubernetes adds value and when VMs, managed containers or serverless are cheaper and faster. Cites evidence: 46% report lacking training, ~60,000 Kubernetes questions on StackOverflow, and that successful platform teams often stay around 9–12 people. Describes tools and pitfalls: Terraform lifecycle pain, managed cloud services, Docker Swarm vs Kubernetes, and when stateful services or WebAssembly matter.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:10Speaker and topic
- 2:15Kubernetes as Lego set
- 7:10Why Kubernetes fails
- 10:43DevOps misalignment
- 14:14Lack of training effects
- 17:47Security and observability integration
- 20:37Security not Kubernetes' fault
- 22:43When Kubernetes is wrong
- 27:15Kubernetes as platform foundation
- 29:49Kubernetes decision questions
- 35:57Microservices vs monoliths on K8s
- 37:23Serverless vs Kubernetes
- 40:36Team capacity and learning curve
- 43:26Future of cloud native runtimes
related talks
24mYou probably don't need K8S
54mKubernetes for the konfused, a strategy toolkit for normals
39mKubernetes is awesome – but …
04mKubernetes Hype - Do you really need it?
05mYou Probably Don't Need Kubernetes
01h 01mDo We Really Need Kubernetes at the Edge
32mFrom Cloud Naive to Cloud Native – Avoiding Mistakes Everyone Does
01h 16mKubernetes: Your Solution or Your Problem?