Operators and Helm It Takes Two to Tango
summary
Analysis of 102 Go-based operator repos (10+ stars) finds ~50% include Helm charts and many omit CRD YAML or validation, which leads to install failures. Recommendation is to register CRDs in the operator Helm chart using the CRD-install hook, put configurable behavior in values.yaml or ConfigMaps, and embed CRD validation schemas. Also add platform-as-code annotations (usage and composition) so application charts can discover and bind resources; q+ implements a resolver with an q+ aggregated API server, mutating webhook and platform-stack CRD to import runtime values (example: binding a Moodle CR to a Presslabs MySQL service).
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:30What is a Kubernetes Operator
- 3:55Why use Helm
- 7:23Guidelines
- 10:05Helm Hook
- 11:23Customization
- 14:06Platform as Code Notations
- 16:15Custom Resources
- 19:40QAPI
- 22:57Import Value
- 24:29Summary
related talks
32mThe Automation Challenge: Kubernetes Operators vs Helm Charts
32mManaging CRDs and Operators in Practice
30mThe Automation Challenge: Kubernetes Operators vs Helm Charts
47mThe Automation Challenge: Kubernetes Operators vs Helm Charts
43mLessons learned writing 10+ Kubernetes Operators
27mDeploying Databases on Kubernetes: Helm vs. Operators - Eric Schäffer and Manuel Swiercz
29mHelm Your Way with Kubernetes
38mHelm: The Charts and the Curious