Helm — The Package Manager for Kubernetes

What it is

Helm is the package manager for Kubernetes. It uses Charts -- bundles of pre-configured Kubernetes resource definitions -- to define, install, and upgrade applications on any Kubernetes cluster. Helm handles dependency management, templating, and release versioning so you can deploy complex multi-service applications repeatably.

DevOps engineers deploying applications to Kubernetes, platform teams maintaining internal service catalogs, and developers who need reproducible cluster setups use Helm as the standard tool for Kubernetes package management.

How it saves time or tokens

Deploying a multi-service application to Kubernetes requires writing dozens of YAML manifests for deployments, services, config maps, secrets, and ingress rules. Helm Charts package all of these into a single installable unit with configurable values. Upgrading an application becomes a single helm upgrade command instead of manually editing and applying individual manifests. Rollbacks to previous versions are built in.

How to use

1. Install Helm:

brew install helm                          # macOS
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash

1. Add a chart repository and install an application:

helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo update
helm install my-redis bitnami/redis --set auth.password=mypassword

1. Manage releases:

helm list                                  # list installed releases
helm upgrade my-redis bitnami/redis        # upgrade
helm rollback my-redis 1                   # rollback to revision 1

Example

# Chart.yaml -- define your chart
apiVersion: v2
name: my-web-app
version: 1.0.0
description: A web application chart
dependencies:
  - name: postgresql
    version: 12.x.x
    repository: https://charts.bitnami.com/bitnami

# values.yaml -- configurable defaults
replicaCount: 3
image:
  repository: myorg/webapp
  tag: latest
service:
  type: ClusterIP
  port: 80
ingress:
  enabled: true
  hostname: app.example.com

# Install with custom values
helm install my-app ./my-web-app -f production-values.yaml

# Template locally to preview generated manifests
helm template my-app ./my-web-app -f production-values.yaml

Related on TokRepo

• DevOps Tools -- explore DevOps and infrastructure automation tools
• Automation Tools -- discover tools for deployment and workflow automation

Common pitfalls

• Helm 3 removed Tiller (the server-side component from Helm 2). If you see Tiller-related instructions, they are outdated. Helm 3 interacts directly with the Kubernetes API.
• Chart version and app version are different. Chart version tracks the packaging, while appVersion tracks the actual application version inside the chart.
• Sensitive values (passwords, API keys) passed via --set appear in shell history. Use --values with a file or Kubernetes secrets management for production credentials.