Trace Kubernetes resources to owning kro instances via labels, annotations, and managedFields.
npx skills add https://github.com/confighub/cub-scout --skill observe-kro
Please help me install this Agent Skill. Skill: observe-kro Source: https://github.com/confighub/cub-scout/tree/main/skills/observe-kro Command: npx skills add https://github.com/confighub/cub-scout --skill observe-kro
This Skill helps you determine whether a Kubernetes resource is managed by kro, identify which specific kro instance it belongs to, and explain what kind of kro controller activity produced the current field values—without guessing.
Ask the AI to explain a single Kubernetes object and trace it back to its kro instance, for example: "explain deploy/api -n prod and tell me if it is managed by kro and what manager wrote the current fields."
High-intent search queries and answers about installing and using this skill.
To check if a Kubernetes resource is managed by kro, inspect its labels, annotations, and owner-reference chains for matches against kro API groups. The Skill classifies resources as kro-managed by tracing these signals back to the owning kro instance or ResourceGraphDefinition.
The kro.run/applyset manager in managedFields indicates which kro controller wrote the current field values. This Skill attributes writers by checking manager strings like applyset, applyset-parent, or labeller to explain what kro activity caused a specific change.
Trace a Kubernetes object to its kro instance by reading kubectl-derived object metadata and applying kro API group detection. The Skill prioritizes signal sources like labels and ownerReferences, falling back across multiple sources to distinguish kro Instances from ResourceGraphDefinition outputs.
Empty kro label values are skipped during ownership detection, and the Skill falls back to annotations or ownerReference chains to identify the kro instance. It also surfaces limitations when multiple kro labels are present, ensuring accurate attribution without guessing.
Yes, you can diagnose drift on kro-managed applyset writes by analyzing kubectl-derived object metadata and managedFields manager strings. The Skill identifies which kro field manager wrote the data to help pinpoint what caused the current field values.
Yes, troubleshooting kro ownership requires reading kubectl-derived object metadata to detect kro API groups and attribute writers via managedFields. The Skill applies this metadata to distinguish kro instances from definitions using label, annotation, and ownerReference fallbacks.
confighubClassify Kubernetes resource ownership via ownerReferences and managedFields signals.
JetBrainsDiagnose Gradle and Spring classpath conflicts in Kotlin applications.
HCMUTE-RTICImplement GitOps workflows for declarative Kubernetes deployments with ArgoCD and Flux CD.
confighubDiagnose Flux-managed Kubernetes resources by tracing ownership to Kustomizations or HelmReleases.
