Closing the Developer Experience Gap of your Container Platforms
summary
Claims a platform can hide Kubernetes complexity by wiring together Cloud Native Buildpacks, kpack, Knative and Cartographer so source-to-URL is automated and operator-controlled. Demo shows kp image create building an image, automatic rebases when stacks update, kservice deploying in ~11 seconds with TLS, and Knative scaling from zero to many pods on load. Cartographer provides asynchronous, event-driven CI/CD integration and Backstage supplies a single UI — the demos run end-to-end.
AI-written summary · about
chapters (9)
- 0:00Developer experience gaps
- 2:31Kubernetes needs higher abstractions
- 5:21App-aware platform concept
- 8:30Cloud Native Build Packs
- 10:15KPAC for container updates
- 16:38Serverless runtime KNative
- 24:00Cartographer for CI/CD
- 28:36Backstage for portals
- 29:37Closing and tools overview
related talks
30mClosing the Developer Experience Gap of your Container Platforms
36mClosing the Developer Experience Gap of your Container Platforms
54mClosing the Developer Experience Gap in the Kubernetes Ecosystem
32mBringing Buildpacks to Kubernetes
20mWhat Does A Platform On Kubernetes Look Like?
36mHow to Build Cloud-Native Platforms with Kubernetes
52mCloud Native Developer Experience in 2025
38mBringing Cloud Native Buildpacks to Kubernetes - Dr Nic Williams, Stark & Wayne