debug-flux-reconciliation

Diagnose Flux reconciliation issues in Anton through an ordered diagnostic path.

3|Updated May 13, 2025

Search Tags:#diagnostics #kubectl #reconciliation #flux #sops #helmrelease #kustomization

Ready to run

npx skills add https://github.com/wcygan/anton --skill debug-flux-reconciliation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-flux-reconciliation
Source: https://github.com/wcygan/anton/tree/main/.claude/skills/debug-flux-reconciliation
Command: npx skills add https://github.com/wcygan/anton --skill debug-flux-reconciliation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and diagnose Flux reconciliation issues in Anton by following an ordered diagnostic path.

Core Features & Use Cases

Ordered triage steps: check source health, kustomization progress, and HelmRelease status to isolate the failure.
Guidance for viewing logs and resources: kubectl describe and flux logs, then verify SOPS decrypts and dependencies.
Safe progression to force reconcile in dependency order only after upstream fixes.

Quick Start

Walk the diagnostic path to identify and fix Flux reconciliation issues in Anton.

Frequently Asked Questions about debug-flux-reconciliation

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

FAQPage Schema

How do I troubleshoot Flux HelmRelease reconciliation failures?▼

To troubleshoot Flux HelmRelease reconciliation failures, check source health first, then inspect HelmRelease status and view flux logs to isolate the issue before attempting a safe force reconcile.

What is the best way to diagnose stalled Flux Kustomization syncs?▼

Diagnosing stalled Flux Kustomization syncs requires an ordered path: verify git source health, check Kustomization progress with kubectl describe, and confirm SOPS decryption blocks are resolved.

Why does my Flux Kustomization stop progressing after a SOPS decryption block?▼

Flux Kustomization stops progressing after a SOPS decryption block when upstream dependencies fail, requiring you to verify SOPS decrypts correctly and resolve git source issues before retrying.

Can I use kubectl to triage non-progressing Flux resources across clusters?▼

Yes, you can use kubectl describe and flux logs to triage non-progressing Flux resources across clusters managed by Anton, verifying dependencies and source health before forcing reconciliation.

When should I force reconcile Flux HelmReleases and Kustomizations?▼

Force reconcile Flux HelmReleases and Kustomizations only after upstream fixes are confirmed, applying force operations in dependency order to safely resolve stalled syncs without repeating failures.