Reducing Boilerplate With Kubernetes Custom Resource Definitions
summary
Manifold replaces repeated YAML with Kubernetes Custom Resource Definitions plus controllers that combine Deployment Service Ingress into a single reconciled object, automatically recreating accidentally deleted components and triggering rollouts when images or secrets change. Initial implementation uses client-go and ends up as thousands of lines of Go; prototyping with meta controller reduces that to tens of lines (JS/Python webhooks). Admission webhooks provide mutating/validating checks; CRD versioning is a noted limitation for larger/long‑lived APIs.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 4:02Current Architecture
- 13:18Custom Resource Definitions
- 15:45Controller
- 17:03MetaController
- 18:43Webhooks
- 21:07Why
- 23:08composability
- 24:03operators
- 27:17Questions
related talks
40mExtending K8s- Introducing Custom Resources, Controllers, Operators & Schedulers
27mDemystifying Why the World Is Built on Kubernetes: Learning To Leverage Bespoke CRDs and Controllers
26mMetaController: Build K8s Controllers as Declarative Intents
36mDesign Conventions You Need to Know When Extending Kubernetes with CRDs
29mEvolving Platform Primitives: Beautiful Platforms With Kro
37mBeyond Kubebuilder - Generating Entire Kubernetes Controller Implementations
40mBootiful Kubernetes Operators
31mKubernetes Operators within Reach of Any Developer