Chart Packaging and Versioning
You'll learn how to bundle your Helm charts into distributable archives and apply semantic versioning to track changes over time.
The Distribution Problem
Once you've built and tested a Helm chart, you need a way to share it—whether with teammates, across environments, or publicly. Think of this like shrink-wrapping a product: you package it into a neat, self-contained unit that can be moved, stored, and distributed reliably.
Packaging Your Chart
Helm packages charts into .tgz (tarball) archives using the helm package command. This creates a versioned, compressed file containing your entire chart directory:
helm package my-chart/
# Output: my-chart-1.0.0.tgz
The package includes all templates, values files, dependencies, and metadata. The filename incorporates the chart name and version from Chart.yaml, making it instantly identifiable.
Semantic Versioning in Action
Helm follows semantic versioning (SemVer): MAJOR.MINOR.PATCH
- MAJOR (1.x.x): Breaking changes that may require user intervention
- MINOR (x.1.x): New features, backward-compatible
- PATCH (x.x.1): Bug fixes, no new features
Update the version field in Chart.yaml before packaging:
version: 1.2.3
Each time you package, increment appropriately based on your changes. This versioning helps users understand update impact and enables safe rollbacks.
Preparing for Repository Distribution
Packaged charts can be uploaded to Helm repositories (HTTP servers with an index file). After packaging multiple versions, generate a repository index:
helm repo index ./packages
This creates index.yaml, cataloging all chart versions and their metadata—essentially a directory that Helm clients use to discover and download charts.
Key Takeaway: Package charts with helm package, follow semantic versioning strictly, and generate repository indexes to enable discoverable, reliable chart distribution across teams and environments.