What problem does it solve?
It reduces the time spent guessing why Flux CD is failing on a live Kubernetes cluster by collecting real cluster signals (Flux status, controller logs, events, and dependency relationships) and turning them into an actionable root-cause report.
Core Features & Use Cases
- Flux installation health validation: Confirms FluxInstance readiness, verifies controller deployment health, summarizes FluxReport reconciliation, and inspects controller logs when controllers are unhealthy.
- Targeted HelmRelease/Kustomization/ResourceSet troubleshooting: Diagnoses failures by tracing from the failing Flux object to its source, dependencies, inventory-managed resources, and underlying pod/container issues.
- Dependency-chain reporting: Produces structured reports that include the resource inspection trail and evidence (status conditions, events, and logs) to pinpoint root causes.
- Live-cluster correctness guardrails: Enforces correct Kubernetes/Flux API versions discovery, warns about Flux-managed resources during manual action attempts, and handles common edge cases like suspended or progressing resources.
Quick Start
Use the gitops-cluster-debug skill to troubleshoot a failing Flux setup by asking: "Debug my cluster because Flux resources are stuck in NotReady and reconcile errors are appearing."