From Kubernetes to PaaS to Developer Control Planes
summary
Argues that as teams adopt full‑cycle development ownership, a new developer control plane layer is needed on top of Kubernetes to restore the PaaS simplicity developers miss. Cites Heroku/Cloud Foundry ease, Argo CD and Argo Rollouts for visible deployments, GitOps as the reconciliation protocol, and a one‑line config demo linking Linkerd and Emissary that actually works. Recommends treating platforms as products, staffing them, investing in UX, and standardizing CRD‑based interoperability for large orgs (examples include Spotify, New Relic, Twitter).
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:12Developers are being told to "shift left"
- 7:23What did I learn?
- 13:21Shout out to the Argo Project
- 14:49Good UX (for platforms)
- 16:22Workflow and interop
- 17:35Tooling interoperability
- 19:43Insights
- 21:51This is the role of a developer control plane
- 23:00Conclusion: What's next for Platforms?
related talks
32mFrom Kubernetes to PaaS to … Err, What’s Next?
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
31mPanel Discussion: Platform and Developer Productivity - Trends and Challenges
30mImproving the Cloud Development Experience: The Good, The Bad...
39mCI/CD, APIs, and Scaling: What Every Cloud Native Developer Needs To Kn...
29mYour platform is not an island: building a platform for your ecosystem
06mKeynote: PlatformOps: It’s all about Developer Experience
44mPlatform Engineering 101: Building Internal Developer Platforms