Kubernetes-style APIs of the Future
summary
Argues that the Kubernetes resource model is an API platform: enforced JSON structure, standard metadata and six verbs so every resource (pods, deployments, services, CRDs) behaves the same. Controllers push individual resources toward desired state, turning combinatorial state explosion into manageable pieces. Describes kubectl apply and declarative spec/status separation, subresources like scale/status, ways to model imperative ops (create a Backup object or increment a counter), and work on generators and aggregated API servers.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:29API standardization needs
- 5:46Kubernetes resource model
- 10:25State complexity in APIs
- 13:39Future of Kubernetes APIs
- 15:49Q&A
related talks
06mExtending the Kubernetes API
40mKubernetes is Your Cloud Control Plane
35mKubernetes as a Platform Framework: Journey from IaC Pipelines to K8s APIs
27mBuilding API Infrastructure in a Decentralized World
19mKeynote: CRDs, No Longer 2nd Class Thing!
36mKubernetes as the Universal Control Plane: From Pods to Multi-Cloud Infrastructure
34mExtending the Kubernetes API: What the Docs Don't Tell You
25mBuilding APIs in a Cloud Native era