First release install
Install an nginx chart into a new namespace called web, then verify release status and list revisions.
DevOps & Tooling / Knowledge library
Helm
kubernetes package manager for app releases
Why learn Helm?
Helm turns raw Kubernetes YAML into reusable, versioned charts so teams can install, upgrade, and roll back applications consistently across environments.
Where it came from
2015: Created at Deis to simplify Kubernetes app deployment. 2016: Helm 2 introduced Tiller for in-cluster release management. 2018: Donated to CNCF, accelerating ecosystem adoption. 2019: Helm 3 removed Tiller and redesigned security/release handling. 2020: Helm became a CNCF graduated project.
- 2015: Created at Deis to simplify Kubernetes app deployment.
- 2016: Helm 2 introduced Tiller for in-cluster release management.
- 2018: Donated to CNCF, accelerating ecosystem adoption.
- 2019: Helm 3 removed Tiller and redesigned security/release handling.
- 2020: Helm became a CNCF graduated project.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Install an nginx chart into a new namespace called web, then verify release status and list revisions.
- Create dev and prod values files for one chart (replicas, resources, service type). Deploy both with clear release names.
- Upgrade a release with a bad image tag, detect failure quickly, and roll back to the previous healthy revision.
- Package a local chart, push it to an OCI registry, then install it from OCI in a clean namespace.
- Add a chart dependency, lock versions, run dependency update, and explain how reproducibility is preserved.
More ways to practice
Parameterize by environment
Create dev and prod values files for one chart (replicas, resources, service type). Deploy both with clear release names.
Safe upgrade and rollback
Upgrade a release with a bad image tag, detect failure quickly, and roll back to the previous healthy revision.
Package and publish
Package a local chart, push it to an OCI registry, then install it from OCI in a clean namespace.
Dependency control
Add a chart dependency, lock versions, run dependency update, and explain how reproducibility is preserved.
Documentation and sources
- Helm Documentation (helm.sh)
- Helm GitHub Repository (github.com)
- Chart Best Practices (helm.sh)
- Helm Commands Reference (helm.sh)
Catalog research notes
- OCI registry workflows are now a mainstream way to publish and pull charts.
- Helm 3 remains the active major line, using caller RBAC instead of Tiller.
- Chart value validation with values.schema.json is widely used in CI pipelines.
- GitOps tools increasingly consume Helm charts directly for declarative delivery.
Connect the ideas
Alternatives
Explore next
Real World Example
Standardizing Microservice Deployments for FinTech Analytics
A mid-sized financial analytics firm managing a distributed platform of thirty microservices across multiple Kubernetes clusters.
The business problem
The engineering team faces configuration drift and deployment inconsistencies, as manual kubectl apply commands lead to environment-specific errors and prolonged release cycles.
How this topic solves it
Helm provides a templating engine that packages Kubernetes manifests into versioned charts, allowing the team to define base configurations once and inject environment-specific values dynamically.
- Create a base Helm chart structure containing templates for deployments, services, and ingress resources.
- Define a values.yaml file to store environment-specific parameters like replica counts and database endpoints.
- Package the chart into a versioned archive using the helm package command.
- Deploy the application to target clusters using helm install, referencing the specific values file for the environment.
- Manage configuration updates by executing helm upgrade to apply changes without manual manifest editing.
This diagram illustrates the transformation of source templates into a running cluster state.
Application manifests and templates
Environment-specific variables
Processes templates with values
Target environment for deployment
- Source Code → injects templates → Helm Engine
- Values File → provides parameters → Helm Engine
- Helm Engine → deploys resources → Kubernetes Cluster
Expected business outcome
The team achieves predictable, repeatable deployments across development, staging, and production environments, significantly reducing manual configuration errors.
Limitations and checks
Helm charts can become overly complex if logic is deeply nested within templates, making them difficult to debug. To check for this, developers should use helm template to inspect the rendered output before applying it to the cluster.