Flux — GitOps Toolkit for Kubernetes Continuous Delivery

What it is

Flux is a CNCF-graduated GitOps toolkit for Kubernetes continuous delivery. It watches Git repositories, Helm repositories, and OCI registries, then reconciles your cluster state to match. When you push a change to Git, Flux applies it to your cluster automatically.

Flux is built as a set of composable controllers: source-controller fetches artifacts, kustomize-controller applies manifests, helm-controller manages Helm releases, and image-automation-controller updates image tags in Git.

How it saves time or tokens

Flux eliminates manual kubectl apply workflows. Every deployment is a Git commit, which means you get audit trails, rollback via git revert, and PR-based approvals for infrastructure changes. No more SSH-ing into bastion hosts to deploy.

The multi-tenancy model lets platform teams define boundaries while application teams self-serve their own namespaces and Helm releases.

How to use

1. Install the Flux CLI: curl -s https://fluxcd.io/install.sh | sudo bash
2. Bootstrap Flux on your cluster: flux bootstrap github --owner=my-org --repository=fleet --path=clusters/production
3. Add a GitRepository source pointing to your app manifests
4. Create a Kustomization resource that reconciles the source to your cluster

Example

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

Related on TokRepo

• DevOps tools -- More CI/CD and infrastructure tools
• Automation tools -- Workflow automation for deployments

Common pitfalls

• Setting prune: true without understanding it will delete resources removed from Git; test in staging first
• Flux reconciliation intervals default to 10 minutes; set shorter intervals for faster feedback loops
• Secrets in Git require SOPS or Sealed Secrets integration; Flux does not handle plain-text secrets safely