Kubernetes is Not for Developers...?
summary
Argues Kubernetes is a substrate for operations not a direct dev tool and that application teams need a productized internal developer platform on top — examples: Kubernetes + Knative, CI/CD supply chains, and VMware Tanzu as concrete stacks; surveys show skills gaps shrinking but developer cycle speed is not improving; building and operating that platform consumes ongoing work and often takes a year or more (plan to double the timeline); recommends forming a platform engineering product team to lift developers from the blinking cursor.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:12Complexity of Kubernetes
- 5:28Micheals background
- 8:05What is Kubernetes
- 11:29The deal with Kubernetes
- 13:28Advantages of Kubernetes
- 16:13State of Kubernetes Survey
- 18:29What Kubernetes is good at
- 19:34Platform as a Service
- 25:47What is a platform
- 27:39Is Kubernetes for Developers
- 35:36Platform Alternatives
- 37:57Conclusion
related talks
06mKeynote: PlatformOps: It’s all about Developer Experience
54mClosing the Developer Experience Gap in the Kubernetes Ecosystem
41mDevelopers do not need Kubernetes
40mThe Elephant in the Kubernetes Room: Team Interactions
32mFrom Cloud Naive to Cloud Native – Avoiding Mistakes Everyone Does
14mKeynote: Kubernetes is Still Hard (for Developers)
28mKubernetes won’t save you
55mHow to develop apps on K8s and not die trying