gitops-cluster-debug

Diagnose Flux reconciliation failures on live Kubernetes clusters.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/devantler-tech/agent-plugins --skill gitops-cluster-debug-devantler-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitops-cluster-debug
Source: https://github.com/devantler-tech/agent-plugins/tree/main/plugins/gitops-kubernetes/skills/gitops-cluster-debug
Command: npx skills add https://github.com/devantler-tech/agent-plugins --skill gitops-cluster-debug-devantler-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill helps operators diagnose Flux and Flux Operator failures on live Kubernetes clusters when GitOps resources stall, fail reconciliation, or drift out of sync.

Core Features & Use Cases

  • Installation Health Checks: Verify FluxInstance readiness, controller deployments, and the cluster-wide FluxReport.
  • Deep Resource Troubleshooting: Trace failing Kustomizations, HelmReleases, sources, ResourceSets, image automation, and notification flows to root cause.
  • Live Cluster Analysis: Inspect status conditions, events, logs, dependencies, and managed resources instead of only local repository files.
  • Use Case: When a HelmRelease is stuck or a Kustomization cannot apply, this skill follows the dependency chain through sources, controllers, and pods to pinpoint whether the issue is auth, manifests, logs, or cluster state.

Quick Start

Ask this skill to inspect the current cluster, verify Flux is healthy, and produce a root-cause report for the failing Flux resource you are troubleshooting.

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 a Flux HelmRelease that is stuck or failing to reconcile?

To troubleshoot a failing Flux HelmRelease, inspect the resource's status conditions, events, and logs. Trace the dependency chain through sources and controllers to pinpoint whether the root cause is authentication, manifest errors, or cluster state.

What is the best way to diagnose Flux GitOps resources drifting out of sync on a live Kubernetes cluster?

Diagnosing Flux GitOps drift on a live cluster requires inspecting status conditions, events, and controller logs. Analyze the FluxReport and trace failing Kustomizations or sources to identify the root cause instead of only checking local repository files.

How do I check if my Flux installation and controllers are healthy?

Check Flux installation health by verifying the readiness of the FluxInstance custom resource and controller deployments. Review the cluster-wide FluxReport to ensure all GitOps controllers are operational and ready for reconciliation.

Does this troubleshooting method work for Flux image automation and notification issues?

Yes, live-cluster troubleshooting covers Flux image automation and notification flows. You can inspect controller logs and trace dependency chains to resolve issues with image policies, ResourceSets, and alert delivery.

Why does my Flux Kustomization fail to apply manifests to the cluster?

A Flux Kustomization fails to apply when there are schema-aware manifest errors, missing dependencies, or invalid source states. Inspect Kubernetes API-version compatibility, resource events, and controller logs to find the exact root cause.

Can I use this approach to debug Flux Operator failures on live clusters?

Yes, you can debug Flux Operator failures by performing Flux Operator discovery and inspecting the FluxInstance readiness. Analyze live cluster events and controller logs to identify why GitOps resources stall or fail reconciliation.