Helm Users! What Flux 2 Can Do For You
summary
Flux v2 uses a running Helm controller to declare and reconcile Helm releases from Git, adding GitOps features like automated drift detection, unified logging and retry logic. Demo boots a cluster with Flux bootstrap and installs WordPress + MariaDB, Jenkins (pinned 3.3.0 then upgraded to 3.3.x via semantic version ranges), Linkerd, Flagger and cert-manager; CRDs require separate handling. Git sync interval is 1 minute and customization interval 10 minutes; webhook receivers trigger immediate reconcile and the demo apps come up and serve traffic.
AI-written summary · about
chapters (11)
- 0:00Introduction to Flux 2
- 1:30Flux and Helm architecture
- 4:43Setting up a GitOps blog
- 7:08Cluster bootstrapping
- 10:02Automated reconciliation
- 13:24Installing Kyverno
- 16:43Debugging Helm releases
- 22:30GitOps webhook setup
- 26:18Deploying applications
- 29:52Service mesh overview
- 31:56Automated upgrades
related talks
32mIntroducing Flux Helm Operator, a GitOps Approach to Helm Operations
20mHelm Charts & Flux Helm Controller
28mReconciling ClickOps and GitOps
39mEnhance Your Kubernetes Experience with GitOps & Flux
09mWelcome + Opening Remarks
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
21mIntroduction to FluxCD
28mWhat's New with Flux?