Automated Helm Deployment Using Custom Controllers and Operators
summary
A small custom controller using Kubernetes client libraries and Helm reconciles a declared release object to the actual Helm release, updating the HelmRelease status and release version until states match, requeuing on failure. A proof of concept built in one afternoon demonstrates changing pods from a pink unicorn to a blue unicorn and shows the HelmRelease status update. The talk compares this approach to Flux and notes the Flux Helm operator already supports rollback of failed releases and validation via HelmRelease status.
AI-written summary · about
related talks
20mHelm Charts & Flux Helm Controller
41mHelm - the Better Way to Deploy on Kubernetes
32mThe Automation Challenge: Kubernetes Operators vs Helm Charts
26mHelm your way with Kubernetes
35mLearn About Helm And Its Ecosystem
47mThe Automation Challenge: Kubernetes Operators vs Helm Charts
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
27mIntro: Helm