k8s-gitops

Check Flux and ArgoCD readiness, then reconcile Kubernetes GitOps resources.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/spigell/my-agents --skill k8s-gitops-spigell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-gitops
Source: https://github.com/spigell/my-agents/tree/main/agents/shared/src/tools/ask_kubernetes_expert/skills/k8s-gitops
Command: npx skills add https://github.com/spigell/my-agents --skill k8s-gitops-spigell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kubernetes GitOps workflows can get out of sync, drift from the desired state, or fail reconciliation after changes, leaving teams unsure what to check and how to recover quickly.

Core Features & Use Cases

  • Flux CD visibility and reconciliation: List Flux kustomizations and sources to confirm readiness, then reconcile kustomizations or HelmReleases when drift is detected.
  • ArgoCD app management: List ArgoCD applications, fetch app status for diagnostics, and trigger sync/refresh operations to converge to the target state.
  • Operational troubleshooting playbooks: Use structured checks for common failure patterns like source not ready, failed kustomizations, and OutOfSync/Degraded states.

Quick Start

Tell the AI: Check Flux sources readiness in flux-system and reconcile any out-of-date kustomizations for my git change, then confirm the result in ArgoCD app status.

Frequently Asked Questions about k8s-gitops

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

FAQPage Schema
Why does my Flux kustomization show drift after a git change?

ArgoCD applications get stuck in OutOfSync or Degraded states when source readiness fails or reconciliation encounters errors. You can diagnose these states by fetching app status and triggering sync or refresh operations to converge the cluster to the target state.

What's the best way to reconcile out-of-date Flux kustomizations?

No, Flux and ArgoCD GitOps troubleshooting does not require external dependencies. It operates using context-aware parameters with kubectl-based tooling to list sources and apps, verify readiness, and reconcile or sync directly within your continuous delivery workflows.

Can I suspend and resume ArgoCD applications during deployment troubleshooting?

Kubernetes GitOps reconciliation troubleshooting checks common failure patterns like source not ready, failed kustomizations, and OutOfSync or Degraded application states. These structured checks verify sync and source readiness before taking corrective reconciliation actions.

How do I trigger ArgoCD sync to converge an OutOfSync application?

To manage Kubernetes GitOps drift, you check sync and source readiness across Flux and ArgoCD before taking corrective actions. This involves listing sources and apps, verifying readiness, and triggering reconciliation, sync, or refresh operations to converge the cluster.

Does Flux and ArgoCD GitOps troubleshooting require external dependencies?

Kubernetes GitOps reconciliation troubleshooting checks common failure patterns like source not ready, failed kustomizations, and OutOfSync or Degraded application states. These structured checks verify sync and source readiness before taking corrective reconciliation actions.

When should I check Flux source readiness before triggering reconciliation?

To manage Kubernetes GitOps drift, you check sync and source readiness across Flux and ArgoCD before taking corrective actions. This involves listing sources and apps, verifying readiness, and triggering reconciliation, sync, or refresh operations to converge the cluster.