Why Kubernetes Is Inappropriate for Platforms, and How to Make It Better
Channel: CNCF [Cloud Native Computing Foundation]
Date: 2024-03-22

Don't miss out! Join us at our next Flagship Conference: KubeCon + CloudNativeCon North America in Salt Lake City from November 12 - 15, 2024. Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at https://kubecon.io

Why Kubernetes Is Inappropriate for Platforms, and How to Make It Better. - Stefan Schimanski, Upbound; Mangirdas Judeikis, Cast AI; Sebastian Scheele, Kubermatic

The ecosystem is building platforms on Kubernetes now, starting with a hub cluster and then sticking tools for Gitops, for application descriptions and for infrastructure management together, with the goal to create custom APIs for the platform consumers. This works, but hits limits of Kube as a framework quickly. Can we do better? Oh yes, we can! This talk is about extending Kube, adapting its architecture to be a better fit for a world where instead of container orchestration two new personas are at the center: (a) the service & API provider (b) the self-service consumer, often developers or application owners. We focus on 3 dimensions to enable Kube to serve platform engineering better: - from kcp we take the workspace hiararchy as a vastly better multi-tenancy primitive. - cross-workspace API exports and bindings tailor-made for the service provider and consumer personas. - cluster mounting that integrates Kube clusters for a unified user interface and identity management.