From Kubernetes to PaaS to … Err, What’s Next?
summary
Argues that the next layer after Kubernetes is a developer control plane — a platform treated as a product with staffed platform teams, golden paths and UX-led onboarding. Cites concrete tools and wins: Argo CD/Argo Rollouts for deploy/run UX, OpenTelemetry and GitOps as emerging standards, Ambassador/Emissary + Linkerd integrating via a one-line config, Telepresence used for fast feedback, and successful platforms growing bottom-up and developer-led.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:46Spoiler alert!
- 1:56@danielbryantuk (he/him)
- 2:35Developers are being told to shift left
- 4:26Core app/dev platform requirements
- 5:06Kubernetes: Platform foundations
- 9:17What did I learn?
- 10:03Platform as Product: The Golden Path
- 11:33Product-led
- 12:35Ambassador Labs: Drinking our own
- 13:48Good UX (for platforms)
- 16:11Shout out to the Argo Project
- 17:07Workflow and interop
- 18:40Interop Example: Emissary-Ingress & Linkerd
- 20:16The need for a platform control plane emerges
- 21:52Building the golden path(s)
- 22:55Ambassador Labs Podcast Insights
- 26:59The need for a developer control plane (DCP)
- 27:13The CNCF ecosystem is the foundation for a modern developer control plane
- 28:00From Kubernetes to Paas to... Golden Paths
related talks
24mFrom Kubernetes to PaaS to Developer Control Planes
28mPanel: Emerging Trends in Cloud Engineering: Platform as product, APIs, self-service & more
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
12mUnveiling the Future: Navigating Cloud Strategy, Platform Engineering, and Architectural Evolution
35mKubernetes as a Platform Framework: Journey from IaC Pipelines to K8s APIs
15mPaaS isn’t enough: your internal platform in Multi Cloud
59mLessons from Running Developer Platforms & Communities
26mLessons Learned from 7 years of Running Developer Platforms