gitops-cluster-debug

Diagnose failing Flux CD GitOps resources on live Kubernetes clusters.

Updated May 19, 2026
One-click install
npx skills add https://github.com/blouargant/yoke-registry --skill gitops-cluster-debug-blouargant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitops-cluster-debug
Source: https://github.com/blouargant/yoke-registry/tree/main/skills/DevOps/gitops-cluster-debug
Command: npx skills add https://github.com/blouargant/yoke-registry --skill gitops-cluster-debug-blouargant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

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."

Frequently Asked Questions about gitops-cluster-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Flux CD HelmRelease failures on a live Kubernetes cluster?

Troubleshoot Flux CD HelmRelease failures by analyzing reconciliation states, tracing dependency chains, and inspecting underlying pod issues to produce a structured root-cause report. It collects live cluster signals like controller logs and events to pinpoint why resources are stuck.

Why are my Flux Kustomization resources stuck in a NotReady state?

Flux Kustomization resources appear in a NotReady state due to source errors, dependency chain issues, or image pull backoffs. Diagnosing the live cluster involves checking FluxReport status conditions and tracing the failing object to its source inventory.

What's the best way to debug GitOps reconciliation errors without applying changes?

Debug GitOps reconciliation errors safely by inspecting live Kubernetes resources and analyzing logs without applying changes. The process discovers API versions, validates FluxInstance readiness, and warns about Flux-managed resources during manual action attempts.

Can I diagnose Flux controller health and image pull backoff issues on a live cluster?

Diagnose Flux controller health and image pull backoff issues by verifying controller deployment readiness and inspecting controller logs. The troubleshooting process handles common edge cases like suspended or progressing resources to identify the root cause.

Does troubleshooting Flux GitOps require flux-operator-mcp tooling for cluster connectivity?

Troubleshooting Flux GitOps requires flux-operator-mcp tooling for cluster connectivity to perform API version discovery, live resource inspection, and log analysis. This tooling emits structured root-cause reports based on real cluster signals.