This is a complete, hands-on Helm cheat sheet: install, configure, operate, automate and secure it - with copy-paste commands grouped by task. Bookmark it for day-to-day work, incidents and interviews alike.
Helm packages Kubernetes manifests into versioned, parameterized 'charts' so you can install, upgrade and roll back an entire application with a single command and a values file.
Why you reach for it
- One versioned artifact for a whole app instead of a pile of raw YAML
- Environment differences captured in values files, not copy-pasted manifests
- Atomic upgrades and one-command rollbacks to a previous release
Installation
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
helm version
helm create mychart # scaffold a new chartConfiguration reference
A templated Deployment snippet plus its values.yaml.
# templates/deployment.yaml
spec:
replicas: {{ .Values.replicaCount }}
template:
spec:
containers:
- name: {{ .Chart.Name }}
image: "{{ .Values.image.repo }}:{{ .Values.image.tag }}"
---
# values.yaml
replicaCount: 3
image:
repo: ghcr.io/acme/web
tag: "1.0"Core commands you use daily
helm upgrade --install web ./mychart -n prod --create-namespace \
-f values.prod.yaml --atomic --wait
helm history web -n prod
helm rollback web 1 -n prodRepositories
helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo update
helm search repo nginx
helm show values bitnami/nginxReleases
helm upgrade --install web ./chart -n prod --create-namespace --atomic --wait
helm list -A
helm history web -n prod
helm rollback web 1 -n prod
helm uninstall web -n prodAuthor & validate
helm create mychart
helm lint ./mychart
helm template web ./mychart -f values.prod.yaml | kubeconform -strictUse it in CI/CD
Lint and template charts in CI before they ever reach a cluster.
- run: helm lint ./mychart
- run: helm template web ./mychart -f values.prod.yaml | kubeconform -strictBest-practice checklist
- Pin dependency versions in Chart.yaml and commit Chart.lock
- Use --atomic and --wait so failed upgrades roll back automatically
- Validate rendered output with kubeconform/kube-linter in CI
Common pitfalls to avoid
- Un-pinned chart dependencies drifting between environments
- Putting secrets in values.yaml committed to Git
- Overusing complex template logic until charts become unreadable
Security quick wins
- Keep secrets out of values; use SOPS, Sealed Secrets or an external secret store
- Review chart provenance and prefer signed charts from trusted repos
Works well with
- Kubernetes - Declarative orchestration for containers at scale - self-healing, rolling updates and service discovery.
- Argo CD - GitOps continuous delivery for Kubernetes - Git is the source of truth, the cluster is reconciled to match.
- kustomize
A cheat sheet is muscle memory on paper - keep it close until the commands live in your fingers.
Want senior help putting Helm to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.