FluxCD — GitOps Toolkit for Kubernetes Continuous Delivery

FluxCD: GitOps Operator for Kubernetes

FluxCD is a set of continuous and progressive delivery solutions for Kubernetes that are open and extensible. As a CNCF graduated project, Flux implements the GitOps principles — using Git as the single source of truth — through a collection of Kubernetes controllers and APIs.

Key Features

• Multi-source support: Sync from Git repositories, Helm repositories, OCI registries, and S3-compatible buckets
• Kustomize and Helm native: First-class support for both Kustomize overlays and Helm charts without extra wrappers
• Image automation: Automatically update container image tags in Git when new images are pushed to a registry
• Notification controller: Send alerts to Slack, Teams, PagerDuty, and other systems on reconciliation events
• Multi-tenancy: Built-in tenant isolation with fine-grained access control across namespaces
• Progressive delivery: Integrates with Flagger for canary, A/B, and blue-green deployments
• Bootstrapping: Single command to install Flux and configure it to manage itself from Git
• SOPS encryption: Native support for encrypting secrets stored in Git using Mozilla SOPS

Use Cases

• GitOps cluster management: Declaratively manage all cluster resources from Git with automatic drift detection
• Helm release management: Manage Helm chart versions, values, and upgrades through GitOps workflow
• Multi-cluster fleet management: Use a single Git source to manage many clusters with environment-specific overlays
• Automated image updates: Close the loop on CI/CD by having Flux update image tags in Git after new builds
• Secret management: Securely store encrypted secrets in Git using SOPS with age or PGP keys

Quick Start

Bootstrap Flux onto your cluster with GitHub:

# Install the Flux CLI
curl -s https://fluxcd.io/install.sh | sudo bash

# Check prerequisites
flux check --pre

# Bootstrap with GitHub
flux bootstrap github \
  --owner=your-org \
  --repository=fleet-infra \
  --branch=main \
  --path=clusters/my-cluster \
  --personal

Create a GitRepository and Kustomization source:

apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
  name: my-app
  namespace: flux-system
spec:
  interval: 1m
  url: https://github.com/your-org/my-app
  ref:
    branch: main
---
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: my-app
  namespace: flux-system
spec:
  interval: 10m
  path: ./k8s/overlays/production
  prune: true
  sourceRef:
    kind: GitRepository
    name: my-app

Comparison with Alternatives

Feature	FluxCD	ArgoCD	Jenkins X
UI	Weave GitOps (optional)	Built-in rich UI	Built-in UI
Image automation	Native controller	Requires plugins	Built-in
Secret management	SOPS native	Sealed Secrets	Vault integration
Helm support	Native HelmRelease CRD	Native	Native
Multi-tenancy	Namespace-scoped	Project-based	Team-based

vs ArgoCD: Flux is more lightweight and Kubernetes-native in design, using CRDs and controllers exclusively. ArgoCD has a richer UI and application grouping. Flux v2’s image automation is a significant advantage for teams wanting full GitOps loop closure. Many large organizations run both together.

vs Jenkins X: Jenkins X is a full CI/CD platform built on Kubernetes, while FluxCD focuses specifically on the CD/GitOps side. Flux is simpler to operate and compose with other tools, whereas Jenkins X provides more opinionated CI pipelines out of the box.

FluxCD is an excellent choice for platform teams who prefer CLI-first workflows, need strong multi-tenancy, or want tight integration with Kustomize and Helm without additional abstraction layers.