helm-charts

Create and manage Helm charts for Kubernetes application deployment with templates, values, and hooks.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill helm-charts-kalilurrahman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: helm-charts
Source: https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts/tree/main/02-devops-infra/helm-charts
Command: npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill helm-charts-kalilurrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Packaging Kubernetes applications for repeatable, versioned deployment is error-prone when done with raw YAML. This Skill produces a complete Helm chart with environment-agnostic defaults, production-hardened templates, and a tested upgrade and rollback workflow. ## Core Features & Use Cases - Full Chart Scaffold: Generates Chart.yaml, values.yaml, and templates for deployment, service, ingress, configmap, HPA, PDB, and service account. - Reusable Named Templates: Provides _helpers.tpl with standard labels, selectors, fullname, and image reference helpers following Helm conventions. - Production Safety Defaults: Enforces resource limits, read-only root filesystem, non-root execution, pod anti-affinity, PodDisruptionBudget, and zero-downtime rolling updates. - Lifecycle Operations: Covers linting, dry-run rendering, install, upgrade, rollback, history, and helm test hooks. - Use Case: You need to deploy a new microservice to staging and production. Use this Skill to generate a chart with per-environment values files, then run helm lint, helm template, and helm upgrade --wait in CI. ## Quick Start Ask the AI to create a Helm chart for your application with staging and production values files, autoscaling, and a health-check test pod.

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?

Start with helm create to scaffold the chart, then define all tunables in values.yaml and write templates for deployment, service, ingress, and HPA. Validate with helm lint and helm template --debug before installing with helm install --wait.

How do I manage different environments with Helm values files?

Keep environment-agnostic defaults in values.yaml and create override files like values-staging.yaml and values-production.yaml. Pass the environment file with -f during helm install or helm upgrade, and use --set for one-off overrides like image tags.

How do I roll back a failed Helm deployment?

Use helm rollback with the release name and revision number, for example helm rollback my-app 1 --namespace production. Check available revisions first with helm history, and always bump the chart version on every change so rollbacks stay auditable.

Why do my pods not restart when a ConfigMap changes in Helm?

Kubernetes does not restart pods when a ConfigMap updates. Add a checksum annotation like checksum/config computed with sha256sum of the configmap template to the deployment pod spec, which forces a rolling restart whenever the config content changes.

Should I hardcode secrets in Helm values files?

No, never hardcode secrets in values files. Use ExternalSecrets, Vault, or sealed secrets instead, and reference them through secretKeyRef in templates. The chart can optionally create a Secret resource, but production deployments should source secrets externally.