skills.rest
fleet-infra
fleet-infraOFFICIAL
Explore all skills by this author →
WebsiteGitHub

gitops-cluster-debug

Diagnose Flux CD reconciliation errors and generate root-cause reports.

1|Updated Apr 13, 2026
Search Tags:#debugging#logs#kubernetes#diagnostics#flux#root-cause-analysis#fluxcd
One-click install
npx skills add https://github.com/fleet-infra/gitops --skill gitops-cluster-debug-fleet-infra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitops-cluster-debug
Source: https://github.com/fleet-infra/gitops/tree/main/.agents/skills/gitops-cluster-debug
Command: npx skills add https://github.com/fleet-infra/gitops --skill gitops-cluster-debug-fleet-infra

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Debug Flux CD on live Kubernetes clusters using the Flux MCP server to identify unhealthy resources, inspect operator logs, and validate reconciliation health.

Core Features & Use Cases

  • Debugs Flux installation health on live clusters and reports readiness, version, and controller status.
  • Inspects Flux resource status, reads controller logs, traces dependency chains, and performs installation health checks.
  • Generates root-cause analysis reports to guide remediation when users report failing, stuck, or not-ready Flux resources on a cluster.

Quick Start

Debug a Flux deployment on a live cluster by connecting to the flux-operator-mcp server and inspecting Flux resources and controller logs.

Frequently Asked Questions about gitops-cluster-debug

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

FAQPage Schema
How do I debug Flux CD reconciliation errors on a live Kubernetes cluster?▼

Debug Flux CD reconciliation errors by connecting to the Flux MCP server to read failing resources, inspect controller logs, analyze status conditions, and generate a structured root-cause analysis report.

Why are my Flux resources stuck in a not-ready state on Kubernetes?▼

Flux resources stuck in a not-ready state are diagnosed by tracing dependency chains and analyzing status conditions via the Flux MCP server, which produces a root-cause report identifying the failing controller or configuration issue.

How do I check Flux installation health and controller status on a live cluster?▼

Check Flux installation health by using the Skill to connect to the live cluster via the Flux MCP server, which reports readiness, version information, and the operational status of all Flux controllers.

Can I trace Flux CD dependency chains to find the root cause of failing reconciliations?▼

Yes, you can trace Flux CD dependency chains to find root causes by reading Flux resources and controller logs through the Flux MCP server, allowing you to pinpoint exactly where the reconciliation dependency chain breaks.

What do I need to connect to the flux-operator-mcp server for diagnostics?▼

To perform Flux diagnostics you need a live Kubernetes cluster with Flux CD installed, allowing the Skill to interface with the flux-operator-mcp server to inspect resources, read logs, and validate installation health without additional dependencies.

Related Skills

Explore More Software Engineering Skills→
Sandesh-SolabannavarSandesh-Solabannavar

gitops-cluster-debug

Diagnose Flux CD issues on live Kubernetes clusters with root-cause analysis.

Community
Advanced
foxj77foxj77
18

flux-troubleshooting

Diagnose Flux CD reconciliation failures using controller logs and Git-based fixes.

Community
Advanced
ppiankovppiankov

logtap

Captures, triages, and analyzes ephemeral Kubernetes logs in real-time via CLI and sidecar injection.

Community
Advanced
jrmatherlyjrmatherly

cluster-ops

Inspect and recover Spacebot deployments in a Talos Kubernetes cluster.

Community
Advanced