Flux CD
Flux CD is a set of Kubernetes controllers that keeps a cluster aligned with configuration from Git or another declared source. You review and record the desired state, then Flux repeatedly detects and corrects differences.
itCloud native tools and technologies | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Flux CD
Flux CD applies GitOps to Kubernetes. You declare the state you want in version-controlled configuration. Controllers inside the cluster fetch that configuration and reconcile the cluster toward it.
This model changes the delivery path. A continuous integration system can build and test an image, then update a repository. Flux pulls the declared state from that source. It does not need a deployment job with broad, permanent access to every cluster.
The central mental model
Think in terms of a control loop:
- You record desired state in a source.
- A Flux source controller fetches that state as an artifact.
- A reconciler builds or interprets the artifact.
- The reconciler compares desired and observed state.
- It applies changes and reports status.
- The loop runs again at the configured interval or after an event.
Reconciliation is the key idea. Flux does not run a one-time deployment and walk away. It continues checking. A corrected Git commit changes the desired state. A manual cluster edit creates drift that a later reconciliation can reverse when pruning and ownership settings cover that resource.
The controllers
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://fluxcd.io/
Supports
- Flux as continuous delivery for Kubernetes through GitOps
- Official documentation and project scope
- https://fluxcd.io/flux/concepts/
Supports
- Reconciliation, desired state, controllers, sources, Kustomization, HelmRelease, and bootstrap
- GitOps Toolkit architecture and vocabulary
- https://fluxcd.io/flux/get-started/
Supports
- Bootstrap prerequisites and walkthrough
- Initial GitRepository and Kustomization sync
- Sample application deployment and Kustomize patches
- https://fluxcd.io/flux/flux-e2e/
Supports
- Core and optional controller responsibilities
- Bootstrap sequence and source-to-reconciler relationships
- Status and revision evidence across the delivery chain
- https://fluxcd.io/flux/installation/
Supports
- Bootstrap as the recommended installation
- Self-management from Git and provider integrations
- https://fluxcd.io/flux/installation/configuration/optional-components/
Supports
- Default, minimum, and optional controller sets
- https://fluxcd.io/flux/components/source/
Supports
- Source controller artifact acquisition and interface
- Git, OCI, bucket, and Helm source families
- Authentication, source verification, schedules, events, and artifacts
- https://fluxcd.io/flux/components/kustomize/kustomizations/
Supports
- Manifest build and apply reconciliation
- Source references, paths, pruning, dependencies, health checks, service accounts, suspension, inventory, revisions, and conditions
- https://fluxcd.io/flux/components/helm/helmreleases/
Supports
- HelmRelease chart and values configuration
- Install, upgrade, testing, remediation, drift detection, suspension, and status
- https://fluxcd.io/flux/components/image/
Supports
- Image repository scanning and image policy reflection
- YAML updates and Git commits from image automation
- https://fluxcd.io/flux/monitoring/alerts/
Supports
- Controller events, providers, alerts, severities, and external notification services
- https://fluxcd.io/flux/monitoring/
Supports
- Official monitoring paths for alerts, metrics, logs, and events
- https://fluxcd.io/flux/monitoring/metrics/
Supports
- Controller Prometheus metrics and custom-resource metrics
- https://fluxcd.io/flux/security/
Supports
- Controller authorization model, security configuration, and multi-tenancy concerns
- https://fluxcd.io/flux/installation/configuration/multitenancy/
Supports
- Tenant reconciliation through service-account impersonation
- Shared-cluster isolation controls
- https://fluxcd.io/flux/guides/mozilla-sops/
Supports
- SOPS encryption and Flux decryption for Kubernetes Secrets
- Supported key providers and key-separation requirements
- https://github.com/sindresorhus/awesome
Supports
- Starting index used for required awesome-list discovery
- https://github.com/weaveworks/awesome-gitops
Supports
- Discovery of Flagger, SOPS, Kustomize, and Helm as relevant GitOps ecosystem projects
- https://docs.flagger.app/
Supports
- Progressive delivery strategies, metric analysis, and Flux integration
- https://github.com/getsops/sops
Supports
- Encrypted file formats and supported key services
- Editing and protecting structured secret values
- https://kustomize.io/
Supports
- Template-free Kubernetes configuration customization
- Declarative overlays and Kubernetes integration
- https://helm.sh/docs/intro/introduction/
Supports
- Helm charts, repositories, values, and releases
