helm

Create, lint, test, and package Helm charts for Kubernetes deployment.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill helm-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: helm
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/helm
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill helm-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authoring Helm charts involves many moving parts — Chart.yaml metadata, templated manifests, helper definitions, subchart dependencies, and validation — and mistakes often surface only at deploy time. This Skill guides chart creation, testing, and packaging so charts are linted, rendered, and dry-run validated before release. ## Core Features & Use Cases - Chart scaffolding and structure: Generate charts with helm create and configure Chart.yaml with apiVersion, SemVer versioning, and dependency declarations. - Validation and testing: Run helm lint --strict, helm template rendering, dry-run installs, and chart test hooks to catch errors before deployment. - Packaging and distribution: Package charts with dependency updates, index chart repositories, and push to OCI registries. - Use Case: You need to ship an application to Kubernetes with a PostgreSQL backend. Use this Skill to scaffold the chart, declare the Bitnami PostgreSQL subchart dependency, write _helpers.tpl naming templates, lint and dry-run the chart, then package and push it to an OCI registry. ## Quick Start Ask the assistant to create a new Helm chart for your application, add a dependency, and validate it with helm lint and a dry-run install.

Frequently Asked Questions about helm

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

FAQPage Schema
How do I create a Helm chart from scratch?

Run helm create mychart to scaffold Chart.yaml, values.yaml, a templates directory with _helpers.tpl, and test hooks. Then edit Chart.yaml to set the chart version, appVersion, and any dependencies before customizing the templates.

How to test a Helm chart before deploying?

Run helm lint with --strict to catch warnings, helm template to render manifests locally, and helm install with --dry-run --debug for server-side validation. You can also define test pods with the helm.sh/hook: test annotation and run them via helm test.

How do I add dependencies or subcharts to a Helm chart?

Declare dependencies in Chart.yaml with name, version, and repository, then run helm dependency update to download them into the charts directory. Configure subchart values under the dependency's key in the parent values.yaml and use condition fields to toggle them.

Can I publish Helm charts to an OCI registry?

Yes, Helm 3.8 and later supports OCI registries. Package the chart with helm package, then push it using helm push mychart-0.1.0.tgz oci://registry.example.com/charts. Traditional chart repositories with helm repo index are also supported.

What is the difference between chart version and appVersion?

The version field in Chart.yaml is the SemVer version of the chart itself and changes whenever templates change. The appVersion field tracks the version of the application being deployed and is informational, often used to set default image tags.