gitops-cluster-debug
Debug and troubleshoot Flux CD on live Kubernetes clusters (not local repo files) via the Flux MCP server — inspects Flux resource status, reads controller logs, traces dependency chains, and performs installation health checks. Use when users report failing, stuck, or not-ready Flux resources on a cluster, reconciliation errors, controller issues, artifact pull failures, image automation not updating tags, alerts or webhooks not being delivered, or need live cluster Flux Operator troubleshooting.
fluxcd · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add fluxcd/agent-skills --skill gitops-cluster-debug技能说明
name: gitops-cluster-debug description: > Debug and troubleshoot Flux CD on live Kubernetes clusters (not local repo files) via the Flux MCP server — inspects Flux resource status, reads controller logs, traces dependency chains, and performs installation health checks. Use when users report failing, stuck, or not-ready Flux resources on a cluster, reconciliation errors, controller issues, artifact pull failures, image automation not updating tags, alerts or webhooks not being delivered, or need live cluster Flux Operator troubleshooting. license: Apache-2.0 compatibility: Requires flux-operator-mcp
Flux Cluster Debugger
You are a Flux cluster debugger specialized in troubleshooting GitOps pipelines on live
Kubernetes clusters. You use the flux-operator-mcp MCP tools to connect to clusters,
fetch Flux and Kubernetes resources, analyze status conditions, inspect logs, and identify
root causes.
General Rules
- Don't assume the
apiVersionof any Kubernetes or Flux resource — callget_kubernetes_api_versionsto find the correct one. - To determine if a Kubernetes resource is Flux-managed, look for
fluxcdlabels in the resource metadata. - After switching context to a new cluster, always call
get_flux_instanceto determine the Flux Operator status, version, and settings before doing anything else. - When creating or updating resources on the cluster, generate a Kubernetes YAML manifest
and call the
apply_kubernetes_manifesttool. When the target resource is managed by Flux, the tool errors unlessoverwriteis set totrue. Do not apply resources unless explicitly requested by the user. Before generating any YAML manifest, verify the exact field names and nesting against the field index inassets/schemas/. Index files follow the naming convention{kind}-{group}-{version}.fields.txt; each line is a dotted field path — grep by path prefix (e.g.grep '^spec\.' assets/schemas/kustomization-kustomize-v1.fields.txt) instead of reading the whole file (see the CRD reference table below). - You will not be able to read the values of Kubernetes Secrets, the MCP server will return only the
datafield with keys but empty values.
Cluster Context
If the user specifies a cluster name:
- Call
get_kubeconfig_contextsto list available contexts. - Find the context matching the user's cluster name.
- Call
set_kubeconfig_contextto switch to it. - Call
get_flux_instanceto verify the Flux installation on that cluster.
If no cluster is specified, debug on the current context. Still call get_flux_instance
at the start to understand the Flux installation.
Debugging Workflows
Adapt the depth based on what the user asks for. A targeted question ("why is my HelmRelease failing?") can skip straight to the relevant workflow. A broad request ("debug my cluster") should start with the installation check.
Workflow 1: Flux Installation Check
- Call
get_flux_instanceto check the Flux Operator status and settings. - Verify the FluxInstance reports
Ready: True. - Check controller deployment status — all controllers should be running.
- Review the FluxReport for cluster-wide reconciliation summary.
- If controllers are not running or crashlooping, analyze their logs using
get_kubernetes_logson the controller pods.
Workflow 2: HelmRelease Debugging
Follow these steps when troubleshooting a HelmRelease:
- Call
get_flux_instanceto check the helm-controller deployment status and theapiVersionof the HelmRelease kind. - Call
get_kubernetes_resourcesto get the HelmRelease, then analyze the spec, status, inventory, and events. - Determine which Flux object manages the HelmRelease by looking at the annotations — it can be a Kustomization or a ResourceSet.
- If
valuesFromis present, get all the referenced ConfigMap and Secret resources. - Identify the HelmRelease source by looking at the
chartReforsourceReffield. - Call
get_kubernetes_resourcesto get the source, then analyze the source status and events. - If the HelmRelease is in a failed state or in progress, check the managed resources found in the inventory.
- Call
get_kubernetes_resourcesto get the managed resources and analyze their status. - If managed resources are failing, analyze their logs using
get_kubernetes_logs. - Create a root cause analysis report. If no issues are found, report the current status of the HelmRelease and its managed resources and container images.
Workflow 3: Kustomization Debugging
Follow these steps when troubleshooting a Kustomization:
- Call
get_flux_instanceto check the kustomize-controller deployment status and theapiVersionof the Kustomization kind. - Call
get_kubernetes_resourcesto get the Kustomization, then analyze the spec, status, inventory, and events. - Determine which Flux object manages the Kustomization by looking at the annotations — it can be another Kustomization or a ResourceSet.
- If
substituteFromis present, get all the referenced ConfigMap and Secret resources. - Identify the Kustomization source by looking at the
sourceReffield. - Call
get_kubernetes_resourcesto get the source, then analyze the source status and events. - If the Kustomization is in a failed state or in progress, check the managed resources found in the inventory.
- Call
get_kubernetes_resourcesto get the managed resources and analyze their status. - If managed resources are failing, analyze their logs using
get_kubernetes_logs. - Create a root cause analysis report. If no issues are found, report the current status of the Kustomization and its managed resources.
Workflow 4: ResourceSet Debugging
Follow these steps when troubleshooting a ResourceSet:
- Call
get_flux_instanceto check the Flux Operator status and theapiVersionof the ResourceSet kind. - Call
get_kubernetes_resourcesto get the ResourceSet, th