loom-fluxcd

# Flux CD GitOps Toolkit ## Overview Declarative GitOps CD: a set of specialized controllers continuously reconcile cluster state toward Git. Flux is CRD-centric with no first-party UI — you drive it with the `flux` CLI and YAML. The controllers, and the CRDs each owns: | Controller | CRDs | Role | | --- | --- | --- | | source-controller | `GitRepository`, `OCIRepository`, `HelmRepository`, `HelmChart`, `Bucket` | Fetch + verify + cache artifacts | | kustomize-controller | `Kustomization` | Build/apply overlays, prune, health-check, `dependsOn` ordering | | helm-controller | `HelmRelease` | Install/upgrade/rollback charts, drift detection | | notification-controller | `Provider`, `Alert`, `Receiver` | Outbound alerts + inbound webhooks | | image-reflector / image-automation | `ImageRepository`, `ImagePolicy`, `ImageUpdateAutomation` | Scan registries, select tags, commit back to Git | The controller separation matters: a `Kustomization` failure is a kustomize-controller concern; a chart failure is helm-controller. Debug the right one. ## When Argo CD vs Flux Both are CNCF-graduated GitOps controllers; the choice is architectural, not feature-parity. | Concern | Flux CD | Argo CD | | --- | --- | --- | | Ordering | `dependsOn` between Kustomizations/HelmReleases + `healthChecks` gate the next | `argocd.argoproj.io/sync-wave` annotations *within* one Application | | Composition | Kustomization tree: a Kustomization applies more Kustomizations | App-of-apps: one root Appli...