Diagnose field-level divergence between Kubernetes live state and GitOps intent.
npx skills add https://github.com/confighub/cub-scout --skill investigate-drift
Please help me install this Agent Skill. Skill: investigate-drift Source: https://github.com/confighub/cub-scout/tree/main/skills/investigate-drift Command: npx skills add https://github.com/confighub/cub-scout --skill investigate-drift
This Skill helps you explain why live Kubernetes state diverges from the intended GitOps/ConfigHub state, focusing specifically on whether the discrepancy is caused by controller reconciliation or by a manual bypass.
Ask it to compare a resource’s intended vs live state and report the divergent fields with the writer/cause, for example: investigate why Deployment or API settings in production differ from the git manifest and identify whether the controller or a human changed them.
High-intent search queries and answers about installing and using this skill.
To find out why your Kubernetes Deployment differs from the git manifest, perform a three-way drift comparison between desired GitOps intent and live state. This classifies per-field divergence using managedFields attribution to identify whether a controller or a manual edit caused the change.
GitOps drift is a field-level divergence between live Kubernetes state and desired git intent. ManagedFields attribution detects manual edits by analyzing the cause and managerHint metadata to classify exactly which field value was written by a human versus a reconciliation controller.
To check if ArgoCD or Flux is still syncing a drifted resource, compare the three-way DRY, WET, and LIVE states. This produces structured mismatch outputs with provenance requirements to determine if the controller is actively managing the divergent fields or if a manual bypass occurred.
Yes, you can identify which specific field value was written by whom in a Kubernetes resource by analyzing managedFields attribution. This provides a per-field cause and managerHint classification, using gitSource and bindingSource provenance to distinguish controller-drift from manual edits.
Yes, this GitOps drift investigation approach works with both ArgoCD and Flux. It diagnoses field-level divergence between live Kubernetes state and desired GitOps intent regardless of the specific controller, using managedFields attribution to pinpoint the cause of the discrepancy.
After identifying who changed a Kubernetes field during a drift investigation, you can use the structured mismatch outputs to plan a response. This evidence supports deciding whether to revert the live state, port the edit back to git, or accept an exception without performing any mutations.
confighubCompare live Kubernetes state against ConfigHub-governed intent across clusters.
AzureDetect configuration drift between Azure resources and stored IaC state.
confighubCompare intended Kubernetes state against live cluster state for drift.
confighubClassify Kubernetes resource ownership via ownerReferences and managedFields signals.
