flux-debugging

name	Flux Debugging
description	Diagnose Flux CD reconciliation failures — stale revisions, failed applies, dependency errors, SOPS decrypt failures. Use when: A kustomization is not Ready, source shows an old commit, Flux events show errors, or changes pushed to git aren't being applied to the cluster. Don't use when: The pod is crashing after Flux successfully applied (use pod-troubleshooting). Don't use for CI build failures (use ci-diagnosis). Don't use for registry/image issues (use zot-registry). Don't use for deploying new changes step-by-step (use gitops-deploy). Outputs: Identified root cause of Flux reconciliation failure with specific remediation commands.
requires	["flux","kubectl"]

Flux Debugging

Routing

Use This Skill When

• flux get kustomization shows Ready=False
• Source revision is stale (old commit hash)
• Flux events show reconciliation errors
• Changes pushed to git aren't appearing in the cluster
• SOPS decryption errors in kustomize-controller logs
• Dependency chain is broken

Don't Use This Skill When

• Pod is crashing (CrashLoopBackOff, OOMKilled) → use pod-troubleshooting
• CI workflow failed before Flux gets involved → use ci-diagnosis
• Image "manifest invalid" or ImagePullBackOff → use zot-registry first
• You're deploying changes and want the full workflow → use gitops-deploy
• You need to understand the Flux setup across all 3 clusters → use flux-ops (dyson)
• The pod is Running and healthy but behaving wrong → use debug-troubleshooting