Minimalist Best Practices in Kubernetes Operators
summary
Gives concrete, actionable rules: use Operator SDK/controller-runtime and enable Prometheus metrics with a one-line change to diagnose queued reconciliations; make CRDs small and prefer content-driven feature flags; turn on metrics and namespace-scope your operator to cut watches and RBAC blast radius; implement predicates/filters and requeue-after instead of tight sync loops; prefer patches/server-side-apply, offload long workflows to external APIs, use multi-stage minimal images, and validate with Operator Framework’s scorecard.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:37What is an operator?
- 4:36Components of an operator
- 7:37General principles
- 9:06Custom Resource Definitions
- 12:37Controller logic
- 16:49Minimizing API load
- 21:55RBAC and security
- 23:00Container best practices
- 23:57Summary and resources
- 26:58Q&A
related talks
32mMinimalist Best Practices in Kubernetes Operators
17mAnti-patterns for Kubernetes Operators
43mLessons learned writing 10+ Kubernetes Operators
36mEssential Patterns For Designing And Implementing Your Operator
24mKubernetes Operators with Go
36mLessons learned writing 10+ Kubernetes Operators - Lars Francke and Jannik Heyl
46mOperators Live in the Past: Designing Reliable Kubernetes Controllers
34mWriting a Kubernetes Operator: the Hard Parts