SYSTEM Cited by 1 source

FluxCD

FluxCD is a CNCF-graduated GitOps continuous-delivery controller for Kubernetes, a peer of ArgoCD. Like ArgoCD, Flux watches a Git repository containing Kubernetes manifests and reconciles cluster state against declared state.

Notable Flux primitives:

• Kustomization — reconciles a Git-sourced Kustomize overlay into the cluster.
• HelmRelease — reconciles a Helm chart release declaratively (version, values, source). Makes Helm charts a GitOps-reconcilable unit without running helm install imperatively.
• Source controllers — GitRepository, HelmRepository, OCIRepository as pluggable manifest sources.

Stub page — expand on future Flux-internals sources.

Seen in

• sources/2025-05-06-redpanda-a-guide-to-redpanda-on-kubernetes — canonical wiki instance of the bundled-GitOps- dependency anti-pattern. Redpanda's customer-facing Kubernetes Operator initially bundled FluxCD as an internal dependency — the operator used Flux to wrap Redpanda's Helm chart and drive lifecycle reconciliation. The bundling sped up operator development but produced customer confusion (divergence from Kubernetes ecosystem norms) and conflicts with customers who already ran their own FluxCD. Redpanda's fix: make Flux optional in v2.3.x, disabled by default in v2.4.x (Jan 2025), and removed entirely in v25.1.x. Canonical argument on this wiki for why bundling a GitOps controller inside another Operator is structurally wrong.

Related

• concepts/gitops — the declarative-state-in-Git property Flux realises
• systems/argocd — sibling CNCF GitOps controller
• systems/helm — common target via HelmRelease
• systems/kubernetes — the target substrate
• systems/redpanda-operator — canonical wiki instance of the bundling anti-pattern
• concepts/bundled-gitops-dependency-anti-pattern