Lightning Talk: Kustomize Your Operator
summary
Using kustomize inside an operator lets the operator ship baseline manifests and accept user-supplied kustomize patches that override any generated workload (Deployments, StatefulSets, Pods) without changing operator code. The peros data store operator (in use since 2022, rewritten 2023) builds kustomize overlays in Go and applies them via kubectl/server-side-apply; users can do PO template override or full resource fragments, roll back by reverting patches, and iterate without rebuilding the operator. Drawbacks: resource shape changes (e.g. Pods → DaemonSet) require converting user patches.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:07What is an operator
- 2:55Beyond operator defaults
- 3:37Naive customization challenges
- 5:02Kustomize for operator patches
- 6:48Kustomize integration
- 8:12Safety with Kustomize patches
- 9:15Patch stability guarantees
- 10:25Workarounds without updates
- 11:07Kustomize benefits summary
- 11:50Live demo resources
- 12:37Q&A
related talks
16mKustomize Your Operator
07mKustomize: Manage K8S manifests natively
32mFrom User To Contributor: A Quick Guide To Kubectl & Kustomize
30mLet's Kustomize Our K8S Deployments with Style!
34mKustomize: Template-Free Configuration Customization for Kubernetes
17mOwn your YAML: extending Kustomize via Plugins
37mCustomizing Kustomize with Client-Side Custom Resources
41mKustomizing Auto DevOps - an Extensible Deploy Stage