observe-kro

What problem does it solve?

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.

Core Features & Use Cases

• Kro-specific ownership detection: Classifies resources as kro-managed by inspecting labels, annotations, and owner-reference chains that match kro API groups.
• Instance vs definition tracing: Distinguishes kro Instance resources from ResourceGraphDefinition outputs, even when labels are missing.
• Writer attribution via managedFields: Identifies which kro field manager wrote the data (applyset, applyset-parent, or labeller), so you can answer “what caused this change?”
• Edge-case handling for real clusters: Skips empty kro label values, falls back across multiple signal sources, and surfaces limitations when multiple kro labels are present.

Quick Start

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."