Platform Engineering Redefined: Evolving Kubernetes Beyond Container Orchestration
summary
Argues Kubernetes hits architectural limits for platform engineering and shows a concrete alternative: adopts kcp workspace hierarchy for real multi‑tenancy, implements cross‑workspace API exports and bindings to separate service provider and consumer concerns, and demos cluster mounting to unify UI and identity across clusters. Cites tools (Argo CD, Flux, Crossplane, Helm), notes KCP is CNCF sandbox with SAP involvement, and describes reproducible API objects and a working multi‑region deployment pattern.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:53VMs to multicloud Kubernetes
- 7:54Kubernetes limitations
- 14:21Kubernetes as platform
- 20:31Platform owners' role
- 27:10User expectations
- 30:03Introducing KCP
- 33:36Q&A
related talks
27mBuilding a Platform Engineering API Layer with kcp
32mBuilding a Platform Engineering API Layer with kcp
18mThe Past, the Present, and the Future of Platform Engineering
01h 15mTutorial: Exploring Multi-Tenant Kubernetes APIs and Controllers With Kcp
05mkcp: Scaling The Kubernetes Control Plane For The Multi-Clust...
19mProduction-Ready Platform Engineering: Build To FAIL
40mThe Elephant in the Kubernetes Room: Team Interactions
26mKubernetes - The Universal Control Plane