k8s-debug-skill-chart-setup

Prepare Kubernetes Helm charts and manifests with canonical labels for debug-skill ConfigMap matching.

Updated May 19, 2026
One-click install
npx skills add https://github.com/blouargant/yoke-registry --skill k8s-debug-skill-chart-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-debug-skill-chart-setup
Source: https://github.com/blouargant/yoke-registry/tree/main/skills/Coding/k8s-debug-skill-chart-setup
Command: npx skills add https://github.com/blouargant/yoke-registry --skill k8s-debug-skill-chart-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It prevents debug skills from being invisible by ensuring your Kubernetes workloads and Helm templates carry the canonical labels that debug-skill selectors rely on.

Core Features & Use Cases

  • Label correctness audit: verifies labels exist on both the workload objects and the pod templates (the runtime matching surface).
  • Immutable selector safety: checks that Deployment selectors use stable, immutable labels and flags cases that must not be edited in-place.
  • Helm helper refactor guidance: provides a pattern for factoring canonical labels into <chart>.labels and <chart>.selectorLabels to avoid drift.
  • Conventional debug-skills ConfigMap layout: instructs where to place chart-owned debug-skill ConfigMaps so authors can drop in failure-mode entries.

Quick Start

Ask the AI to guide you through auditing your chart’s Deployments, StatefulSets, DaemonSets, and pod templates to ensure the required app.kubernetes.io/name and app.kubernetes.io/instance labels are present on the pod template and that spec.selector.matchLabels uses only an immutable subset.

Frequently Asked Questions about k8s-debug-skill-chart-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Kubernetes pod show 0 candidates because no skill's selector matched?

Kubernetes pod selector mismatches occur when debug-skill ConfigMaps cannot find failing pods because required canonical labels like app.kubernetes.io/name are missing from spec.template.metadata.labels. Ensure pod template labels form a superset of spec.selector.matchLabels.

How do I make Helm charts debug-skill ready for Kubernetes workloads?

To make Helm charts debug-skill ready, audit Deployments, StatefulSets, DaemonSets, and CronJobs to ensure spec.template.metadata.labels includes app.kubernetes.io/name and app.kubernetes.io/instance, and that spec.selector.matchLabels uses only an immutable subset.

Can I modify spec.selector.matchLabels on an existing Kubernetes Deployment?

You cannot modify spec.selector.matchLabels on existing Kubernetes Deployments because selectors are immutable. You must recreate the Deployment or ensure stable immutable labels are set during initial chart bootstrapping to avoid breaking debug-skill matching.

What is the best way to factor canonical labels in Helm chart templates?

The best way to factor canonical labels in Helm templates is splitting them into helper functions like chart.labels and chart.selectorLabels to prevent label drift, ensuring pod templates carry required labels while selectors remain immutable.

Does chart bootstrap work with Kubernetes CronJobs for debug-skill label auditing?

Chart bootstrap supports Kubernetes CronJobs for debug-skill label auditing, verifying that spec.template.metadata.labels includes canonical labels and that spec.selector.matchLabels uses an immutable subset across common workload kinds including CronJobs.

Where should I place debug-skill ConfigMaps in a Helm chart?

You should place debug-skill ConfigMaps using a conventional layout within the Helm chart so chart authors can drop in failure-mode entries, ensuring the ConfigMaps can match failing pods by canonical label placement across workload objects.