Helm & Kustomize · Lesson 2 of 7 · 4 min read
Helm fundamentals
Concepts
- Chart — a package of templates plus default values.
- Release — an installed instance of a chart in a namespace with a name; each upgrade creates a new revision.
- Repository — where charts are published: classic HTTP repos (
index.yaml) or OCI registries (ECR, GHCR, Harbor). - Helm 3 removed the old in-cluster Tiller server; Helm talks to the API server with your kubeconfig credentials and stores release state as Secrets (type
helm.sh/release.v1) in the release namespace. - Helm 4 (released November 2025) keeps the same chart format and commands, and adds Kubernetes server-side apply support (
--server-side), more accurate readiness waiting (kstatus) and a rebuilt plugin system (including WebAssembly plugins). Most material on Helm 3 still applies; check plugin and CI flags when upgrading.
Enlarge diagram
Swipe sideways to see all of it, or tap to open it full screen.
Chart layout
orders/
Chart.yaml # name, version (chart), appVersion (app), dependencies
values.yaml # defaults
values.schema.json # optional JSON schema to validate values
templates/
_helpers.tpl # named templates (labels, names)
deployment.yaml
service.yaml
ingress.yaml
hpa.yaml
NOTES.txt # printed after install
tests/test-connection.yaml
charts/ # vendored dependency charts
# Chart.yaml
apiVersion: v2
name: orders
version: 1.6.0 # chart version — bump on any chart change (semver)
appVersion: "2.14.3" # version of the app it deploys (informational, often default image tag)
type: application
dependencies:
- name: redis # a subchart, installed only when redis.enabled is true
version: 1.x.x
repository: oci://123456789012.dkr.ecr.ap-south-1.amazonaws.com/charts
condition: redis.enabled
Everyday commands
helm repo add jetstack https://charts.jetstack.io
helm repo update
helm search repo jetstack/cert-manager --versions
helm show values jetstack/cert-manager > defaults.yaml
helm upgrade --install orders ./orders -n orders --create-namespace \
-f values-prod.yaml --set image.tag=2.14.3 \
--atomic --wait --timeout 10m
helm list -A
helm status orders -n orders
helm history orders -n orders
helm get values orders -n orders # user-supplied values
helm get manifest orders -n orders # what was actually applied
helm rollback orders 7 -n orders
helm uninstall orders -n orders
helm template orders ./orders -f values-prod.yaml # render locally, no cluster
helm lint ./orders
helm diff upgrade orders ./orders -f values-prod.yaml # helm-diff plugin
upgrade --installis idempotent — the standard CI form.--atomicrolls back automatically if the upgrade fails (implies--wait).--waitwaits for resources to be ready;--timeoutbounds it.
Values precedence
From lowest to highest:
Enlarge diagram
Swipe sideways to see all of it, or tap to open it full screen.
- The chart's
values.yaml(and dependency charts' values). - Parent chart values for subcharts (
redis:key in the parent). -f/--valuesfiles, in order — later files override earlier.--set,--set-string,--set-file,--set-json— highest.
Maps merge deeply; lists are replaced, not merged. Setting a key to null removes a default.
--reuse-values reuses the previous release's values and merges --set; --reset-values goes back to chart defaults. Relying on reused values makes state implicit — prefer always passing the full values files from Git.