Introducing Flux Helm Operator, a GitOps Approach to Helm Operations
summary
Flux Helm Operator pairs Flux and a Helm controller to make Kubernetes deployments fully Git-driven: Flux watches git and registries, upgrades image tags by policy, commits changes back to git, and reconciles state; Helm Operator exposes a Release CRD, installs charts from Helm repos or git, purges failed Helm v2 installs and performs automated rollbacks on upgrade failures. It adds garbage collection of removed resources, namespace delegation for multi tenancy, supports Helm v2 and v3, and claims cluster recovery in about 15 minutes.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:39Why GitOps?
- 4:57How to GitOps?
- 11:31Flux Helm Operator
- 12:51Helm Operator - Features
- 15:50Helm Release CRD
- 23:42Flux - Automated Updates
- 26:15Flux multi-tenancy
- 27:56GitOps Pipeline Demo
related talks
37mHelm Users! What Flux 2 Can Do For You
48mDeep Dive: Flux the GitOps Operator for Kubernetes
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
20mHelm Charts & Flux Helm Controller
39mEnhance Your Kubernetes Experience with GitOps & Flux
22mPush to Prod: GitOps Workflows on k8s with FluxCD
29mAccelerating GitOps Adoption with Flux
28mReconciling ClickOps and GitOps