Extending the Kubernetes API
summary
Extending Kubernetes means adding real API types via custom resource definitions and getting full CRUD, watch, validation, auth, optimistic concurrency and CLI support for free by applying a YAML and using kubectl to create and inspect instances. The model intentionally avoids strict ownership and transactions and trades those guarantees for resilient, multi-actor reconciliation. CRDs are portable across clouds and even Raspberry Pis, with about 50 certified platforms and proven use beyond containers, so the extension mechanism works in production today.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:27Pitch
- 0:47API Driven Kubernetes
- 1:31Multiple Actors
- 2:28Graceful Tolerance
- 2:59Mutations
- 4:08Custom Resources
related talks
44mExtending Kubernetes
40mExtension API Server in Kubernetes: When CRD Is Not Enough
36mDesign Conventions You Need to Know When Extending Kubernetes with CRDs
08mKubernetes: The API of Everything
34mExtending the Kubernetes API: What the Docs Don't Tell You
26mKubernetes-style APIs of the Future
38mKubernetes Beyond
29mExtending Kubernetes Resource Model (KRM) Beyond Kubernetes Workloads
