Skip to content
Back to skills

Helm Chart Patterns

ASecurity

Helm chart development patterns for packaging and deploying Kubernetes applications. Use when creating reusable Helm charts, managing multi-environment deployments, or building application catalogs for Kubernetes.

  • 37 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 6, 2026
ai-agentsgobashkubernetestestinggitsecuritydocumentation

Security analysis

A100/100

Pro scans all 10 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add NickCrew/Claude-Cortex --skill helm-chart-patterns --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Helm Chart Patterns?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Helm Chart Patterns
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nickcrew-helm-chart-patterns-claude-cortex/badge)](https://www.skillsdirectory.com/skills/nickcrew-helm-chart-patterns-claude-cortex)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: helm-chart-patterns
description: Helm chart development patterns for packaging and deploying Kubernetes applications. Use when creating reusable Helm charts, managing multi-environment deployments, or building application catalogs for Kubernetes.
keywords:
  - Helm
  - Helm chart
  - Helm deployment
  - Helm release
  - Helm upgrade
  - chart hooks
  - chart packaging
  - chart repository
  - chart template
  - values.yaml
file_patterns:
  - '**/*deployment*.yaml'
  - '**/charts/**'
  - '**/helm/**'
  - '**/k8s/**'
  - '**/kubernetes/**'
confidence: 0.86
---

# Helm Chart Patterns

Expert guidance for developing production-grade Helm charts covering chart structure, templating patterns, multi-environment configuration, dependency management, testing strategies, and distribution workflows for Kubernetes application packaging.

## When to Use This Skill

- Creating reusable Helm charts for applications and services
- Building application catalogs and chart repositories
- Managing multi-environment deployments (dev, staging, production)
- Implementing advanced templating with conditionals and loops
- Managing chart dependencies and subcharts
- Implementing chart hooks for lifecycle management
- Testing and validating chart templates
- Packaging and distributing charts via repositories
- Using Helmfile for multi-chart orchestration

## Core Concepts

### Chart Types
- **Application charts**: Standard deployable charts for your services
- **Library charts**: Reusable template helpers (not directly installable)

### Key Files
| File | Purpose |
|------|---------|
| `Chart.yaml` | Metadata, version, dependencies |
| `values.yaml` | Default configuration |
| `values.schema.json` | Input validation |
| `templates/_helpers.tpl` | Reusable template functions |
| `templates/*.yaml` | Kubernetes manifests |

### Template Essentials
- **Quote strings**: `{{ .Values.name | quote }}`
- **Indent properly**: `{{- toYaml . | nindent 4 }}`
- **Use helpers**: `{{ include "my-app.fullname" . }}`
- **Check nil**: `{{- if .Values.optional }}`

## Quick Reference

| Task | Load reference |
| --- | --- |
| Chart structure & Chart.yaml | `skills/helm-chart-patterns/references/chart-structure.md` |
| Values file patterns | `skills/helm-chart-patterns/references/values-patterns.md` |
| Template patterns & functions | `skills/helm-chart-patterns/references/template-patterns.md` |
| Dependencies & subcharts | `skills/helm-chart-patterns/references/dependencies.md` |
| Hooks & lifecycle | `skills/helm-chart-patterns/references/hooks.md` |
| Testing patterns | `skills/helm-chart-patterns/references/testing.md` |
| Packaging & distribution | `skills/helm-chart-patterns/references/packaging.md` |
| Helmfile multi-chart | `skills/helm-chart-patterns/references/helmfile.md` |
| Best practices checklist | `skills/helm-chart-patterns/references/best-practices.md` |

## Workflow

1. **Structure** - Set up chart directory with Chart.yaml and values.yaml
2. **Template** - Create Kubernetes manifests with Go templating
3. **Helpers** - Extract common patterns into _helpers.tpl
4. **Validate** - Use values.schema.json for input validation
5. **Test** - Lint, template, and run chart tests
6. **Package** - Create .tgz and publish to repository

## Essential Commands

```bash
# Development
helm create my-app          # Scaffold new chart
helm lint ./my-app          # Validate chart
helm template my-app ./my-app  # Render templates

# Dependencies
helm dependency update      # Download dependencies
helm dependency list        # Show dependencies

# Testing
helm install my-app ./my-app --dry-run --debug
helm test my-app

# Distribution
helm package ./my-app
helm repo index . --url https://charts.example.com
helm push my-app-1.0.0.tgz oci://registry.example.com/charts
```

## Common Mistakes

- Forgetting to quote strings in templates
- Not using `nindent` for proper YAML formatting
- Committing secrets to values files
- Missing security contexts (runAsNonRoot, drop capabilities)
- Not pinning dependency versions
- Skipping values.schema.json validation
- Not testing upgrades from previous versions

## Resources

- **Helm Documentation**: https://helm.sh/docs/
- **Chart Template Guide**: https://helm.sh/docs/chart_template_guide/
- **Best Practices**: https://helm.sh/docs/chart_best_practices/
- **Helmfile**: https://github.com/helmfile/helmfile
- **Chart Testing**: https://github.com/helm/chart-testing

Files in this skill

  • SKILL.md4.3 KB
  • references/best-practices.md1.5 KB
  • references/chart-structure.md2.3 KB
  • references/dependencies.md2.4 KB
  • references/helmfile.md2.3 KB
  • references/hooks.md2.5 KB
  • references/packaging.md1.5 KB
  • references/template-patterns.md6.5 KB
  • references/testing.md1.6 KB
  • references/values-patterns.md5.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…