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
Don't Panic
Don't Panic - Flux CD
Flux CD centers on Flux. Flux CD applies GitOps to Kubernetes. You declare the state you want in version-controlled configuration.
Operate from the project's own resources and APIs. Learn how desired state becomes running state, which status conditions matter, and which dependencies (network, storage, identity, certificates) the control plane assumes.
Upgrades, backups, and credential rotation are part of the product, not optional aftercare. Version skew between clients and servers creates failures that look like application bugs. Pin versions and rehearse rollback.
Convenience features reduce boilerplate and widen blast radius. Enable them when you can observe and reverse the expanded surface. Defaults from quickstarts are starting points, not production policy.
Name owners for upgrades, credentials, and disaster recovery before traffic arrives. Unowned control-plane state becomes an outage with no clear pager. Prefer explicit version pins and tested rollback over floating tags that quietly change behavior between deploys.
Name owners for upgrades, credentials, and disaster recovery before traffic arrives. Unowned control-plane state becomes an outage with no clear pager. Prefer explicit version pins and tested rollback over floating tags that quietly change behavior between deploys.
Name owners for upgrades, credentials, and disaster recovery before traffic arrives. Unowned control-plane state becomes an outage with no clear pager. Prefer explicit version pins and tested rollback over floating tags that quietly change behavior between deploys.
Read the Intro for the mental model. Use the Cheatsheet when you need the resource map. Updates and Upstream track the Flux release line that changes these APIs.
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
