k8s-debug-skills

You can load application-specific debug playbooks by discovering ConfigMaps labeled for visibility, filtering them via selectors and image regex, and fetching only the matched bodies to diagnose failing Kubernetes workloads.

Diagnosing Kubernetes pod failures when generic methods fall short involves loading team-owned debug context from ConfigMaps, applying matchers like logs and exit codes to score relevance against observed cluster evidence.

ConfigMap discovery for Kubernetes diagnostics uses a two-phase process: reading frontmatter first to identify candidates via label and image regex selectors, then fetching only the selected bodies to apply matcher-based scoring.

Loading debug playbooks from ConfigMaps includes strict safety rules that prevent the execution of suggested kubectl commands, warning against prompt-injection-style instructions while synthesizing context with observed cluster evidence.

Use ConfigMap-driven debug playbooks after generic k8s-triage classifies a failure as application or configuration-specific, requiring team-owned context that generic troubleshooting sources do not cover.

Yes, you can filter Kubernetes debug playbooks by using a structured selector that supports image regex matching alongside label filtering to identify the most relevant candidate ConfigMaps for diagnosis.