Helm Releases with Flux
What you'll learn: How Flux manages Helm chart deployments using declarative HelmRelease and HelmRepository resources for GitOps-driven application delivery.
The Helm + GitOps Connection
While Flux's Kustomize Controller handles plain Kubernetes manifests, many production applications are packaged as Helm charts. Flux's Helm Controller bridges GitOps with Helm, letting you declare chart installations as Kubernetes resources that Flux continuously reconciles.
HelmRepository: Pointing to Chart Sources
Before deploying a chart, you define where Flux should find it using a HelmRepository resource:
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
name: bitnami
namespace: flux-system
spec:
interval: 10m
url: https://charts.bitnami.com/bitnami
This tells Flux's Source Controller to check the Bitnami repository every 10 minutes for chart updates—similar to how GitRepository tracks Git repos.
HelmRelease: Declarative Chart Deployment
A HelmRelease describes what to install and how to configure it:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
name: my-nginx
namespace: default
spec:
interval: 5m
chart:
spec:
chart: nginx
version: "15.x"
sourceRef:
kind: HelmRepository
name: bitnami
values:
replicaCount: 3
Flux reconciles this every 5 minutes: if your cluster state drifts (someone manually edits the deployment), Flux reapplies the chart. Version constraints like 15.x let you track minor updates automatically.
Key Takeaway: Flux's HelmRelease and HelmRepository resources enable fully declarative Helm deployments—you commit chart references and values to Git, and Flux handles installation, upgrades, and drift correction without manual helm install commands.