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 teams use 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
Install it
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
helm version
helm create mychart # scaffold a new chartA first working config
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"Run and verify
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 prodMistakes to avoid early
- Un-pinned chart dependencies drifting between environments
- Putting secrets in values.yaml committed to Git
- Overusing complex template logic until charts become unreadable
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.