investigate-drift

What problem does it solve?

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.

Core Features & Use Cases

• Three-way drift comparison with attribution: Composes compare three-way (DRY/WET/LIVE) plus compare drift to identify exactly which fields differ and why.
• Per-field “who wrote this” classification: Uses managedFields attribution (cause, managerHint) and provenance (gitSource, bindingSource when connected) to identify controller-drift vs manual-edit vs unknown.
• Investigation-ready evidence: Produces structured mismatch outputs suitable for response planning (revert, port edit back to git, or accept an exception) without performing any mutations.

Quick Start

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.