Demos and production are different sports. This checklist covers what changes when Flux CD has to be reliable, secure and observable under real load.
Security and reliability defaults
- Encrypt secrets with SOPS and let Flux decrypt in-cluster
- Lock down source repos and use least-privilege deploy keys
A production-minded config
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 }Operational best practices
- Set prune:true and sensible intervals per Kustomization
- Use the notification controller to alert on reconcile failures
- Separate infrastructure and app Kustomizations with dependsOn
In production, boring and reproducible beats clever every time.
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.