helm-charts

Author and review Helm charts for packaging Kubernetes applications.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/DeepSpaceCartel/skills --skill helm-charts-deepspacecartel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: helm-charts
Source: https://github.com/DeepSpaceCartel/skills/tree/main/skills/helm-charts
Command: npx skills add https://github.com/DeepSpaceCartel/skills --skill helm-charts-deepspacecartel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing Helm charts that render correctly, upgrade safely, and follow community conventions is error-prone: version bumps get skipped, numeric labels break upgrades, ConfigMap changes never restart pods, and secrets leak into values files. This Skill encodes Helm chart best practices so charts are structured, validated, and upgrade-safe from the start. ## Core Features & Use Cases - Chart structure and versioning: Correct Chart.yaml anatomy, chart SemVer vs appVersion discipline, .helmignore, labels, hooks, and CRD lifecycle rules. - Values design and validation: values.yaml conventions, the image.tag to appVersion fallback pattern, values.schema.json validation, and safe secret handling via existingSecret and secretKeyRef. - Templating and upgrade safety: _helpers.tpl and include patterns, whitespace control, the numeric-label quoting trap, helm lint/template/unittest workflows, --wait/--atomic semantics, and checksum annotations that roll pods on config changes. - Use Case: When packaging a Kubernetes application as a chart, use this Skill to scaffold the chart, design values.yaml, add a values.schema.json, and set up CI rendering checks before the first helm install. ## Quick Start Ask the AI to create a Helm chart for your application with a values.schema.json, standard app.kubernetes.io labels, and a config checksum annotation on the Deployment.

Frequently Asked Questions about helm-charts

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

FAQPage Schema
How do I create a Helm chart for a Kubernetes application?▼

Create the standard layout with Chart.yaml, values.yaml, and a templates/ directory containing your manifests plus _helpers.tpl for named templates. Give every value a working default so helm install succeeds with no overrides, and bump the chart version on every change.

How do I validate Helm chart values with a schema?▼

Add a values.schema.json file at the chart root using JSON Schema 2020-12. Helm validates user-supplied values against it at install and upgrade time, catching typos and wrong types before rendering a broken manifest.

Why does helm upgrade fail with a map[string]string decode error?▼

This happens when a label or annotation value looks numeric, such as an appVersion of 1.27, which YAML parses as a float. Fix it by piping the value through quote, for example {{ .Chart.AppVersion | quote }}.

Why don't pods restart when a ConfigMap changes in Helm?▼

Kubernetes does not restart pods when a mounted ConfigMap or Secret changes. Add a checksum annotation like checksum/config with sha256sum of the rendered ConfigMap to the pod template so a config change triggers a rolling update.

Should CRDs go in templates/ or crds/ in a Helm chart?▼

Put CRDs in the crds/ directory for install-once semantics: Helm installs them but never upgrades or deletes them. Use templates/ only if you accept full lifecycle management, or manage CRDs outside the chart for explicit migration control.

How do I test a Helm chart without a cluster?▼

Run helm lint for convention checks, helm template to render manifests locally, and the helm-unittest plugin to assert on rendered YAML. You can also pipe helm template output to kubeconform to validate against Kubernetes API schemas.