This is a complete, hands-on Flux CD cheat sheet: install, configure, operate, automate and secure it - with copy-paste commands grouped by task. Bookmark it for day-to-day work, incidents and interviews alike.
Flux is a set of Kubernetes controllers that keep clusters in sync with sources like Git, Helm repositories and OCI artifacts, with first-class Kustomize and Helm support.
Why you reach for it
- Composable controllers (source, kustomize, helm, notification)
- Native Helm and Kustomize reconciliation from Git or OCI
- Strong multi-tenant and progressive-delivery support (Flagger)
Installation
curl -s https://fluxcd.io/install.sh | sudo bash
flux check --pre
flux bootstrap github --owner=acme --repository=fleet --path=clusters/prodConfiguration reference
A GitRepository source plus a Kustomization that applies it.
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata: { name: apps, namespace: flux-system }
spec:
interval: 1m
url: https://github.com/acme/deploy
ref: { branch: main }
---
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata: { name: web, namespace: flux-system }
spec:
interval: 5m
path: ./apps/web
prune: true
sourceRef: { kind: GitRepository, name: apps }Core commands you use daily
flux get kustomizations
flux reconcile kustomization web --with-source
flux suspend kustomization webInspect & reconcile
flux get sources git -A
flux get kustomizations -A
flux get helmreleases -A
flux reconcile kustomization web --with-source
flux suspend kustomization web && flux resume kustomization webBootstrap
flux check --pre
flux bootstrap github --owner=acme --repository=fleet --path=clusters/prod --personalUse it in CI/CD
Flux watches Git, so CI just updates manifests and pushes.
flux create image update web --git-repo-ref=apps --path=./apps/web --checkout-branch=mainBest-practice checklist
- Set prune:true and sensible intervals per Kustomization
- Use the notification controller to alert on reconcile failures
- Separate infrastructure and app Kustomizations with dependsOn
Common pitfalls to avoid
- Long reconcile intervals hiding how stale the cluster is
- Forgetting prune:true, so deleted files stay live in the cluster
- No notifications wired up, so failed reconciliations go unnoticed
Security quick wins
- Encrypt secrets with SOPS and let Flux decrypt in-cluster
- Lock down source repos and use least-privilege deploy keys
Works well with
- Argo CD - GitOps continuous delivery for Kubernetes - Git is the source of truth, the cluster is reconciled to match.
- Kubernetes - Declarative orchestration for containers at scale - self-healing, rolling updates and service discovery.
- kustomize
A cheat sheet is muscle memory on paper - keep it close until the commands live in your fingers.
Want senior help putting Flux CD to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.