Kubernetes is Your Platform: Design Patterns For Extens...
summary
Provides concrete patterns and tradeoffs for making controllers extensible, drawn from Cluster API and Kubewarden experience: use multiple controllers with finalizers for pre-delete backups, parent/child layering like Deployment→ReplicaSet, or a tiny API contract using a machineInfrastructureReady status field so infra controllers are swappable. Describes in-process plugins (binaries or WebAssembly) and out-of-process plugins discovered via an extension-manager CR (webhook-style), notes runtime SDK work, RBAC isolation benefits, network failure and debugging costs, and where coordination is required.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:38Designing Extensible Controllers
- 7:23Lessons Learned
- 16:29Extend a Single Controller
- 19:28Binary Compatibility
- 20:33Out of Process Plugin
- 23:31Lesson Learned
- 25:54Organizational Implications
- 28:05How To Document Behavioral Dependencies
- 30:01Conclusion
related talks
26mKubernetes Is A Platform Platform
32mKubernetes as a platform for platforms
31mKubernetes is a Platform Platform
32mLaying the Foundation: Real World Kubernetes Deployment Patterns
48mLeveraging the power of Kubernetes with patterns
28mThe Kubernetes Control Plane for Busy People Who Like Pictures
41mArchitecting Kubernetes-Based Internal Developer Platforms: Essential Patterns...
27mDemystifying Why the World Is Built on Kubernetes: Learning To Leverage Bespoke CRDs and Controllers