Skip to content
Hands-on IT IT Drills

Day 1: The First Release

Goal: Find someone else’s chart, read it, install it with your own values, upgrade it and roll it back – at the end, zot runs as an OCI registry on port 30500. · Duration: approx. 60 min · Prerequisite: Day 0

Briefing

  • Chart = the package (templates, default values, metadata). Release = an installed instance of it, with its own name. Revision = one state of the release.
  • Core idea: manifests = templates + values. For each environment you change only the values.
  • Every upgrade and every rollback creates a new revision. A rollback does not go back; it writes the old state into the log under a new number.
  • Today you install zot from an HTTP repo. From Day 15 on, zot is the registry for your own chart.
 Repo (index.yaml) ──> helm install ──> templates + values ──> manifests ──> API
                        └──> Secret sh.helm.release.v1.zot.v1 (revision 1)

Drill 1: Add a repo and search it

An HTTP repo is a web server with a file index.yaml that lists all charts and versions. Helm downloads it and searches it locally.

# on prod
mkdir -p ~/helm/tag01 && cd ~/helm/tag01
helm repo add zot https://zotregistry.dev/helm-charts
helm repo update
helm search repo zot
helm search repo zot/zot --versions | head -3

Expected:

"zot" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "zot" chart repository
Update Complete. ⎈Happy Helming!⎈
NAME     CHART VERSION  APP VERSION  DESCRIPTION
zot/zot  0.1.135        v2.1.23      A zot registry helm chart for Kubernetes
NAME     CHART VERSION  APP VERSION  DESCRIPTION
zot/zot  0.1.135        v2.1.23      A zot registry helm chart for Kubernetes
zot/zot  0.1.134        v2.1.23      A zot registry helm chart for Kubernetes

CHART VERSION is the version of the package, APP VERSION that of the software inside. The two are independent: between 0.1.134 and 0.1.135, zot stays at v2.1.23. You find public charts on Artifact Hub with helm search hub <name>.

Save your progress? Sign up for free

Drill 2: Read before you install

# on prod
helm show chart zot/zot --version 0.1.134
helm show values zot/zot --version 0.1.134 | grep -A3 '^service:'
helm show values zot/zot --version 0.1.134 | grep -E '^(persistence|mountConfig):'
helm show readme zot/zot --version 0.1.134 | head -5

Expected (abridged):

apiVersion: v2
appVersion: v2.1.23
description: A zot registry helm chart for Kubernetes
name: zot
type: application
version: 0.1.134
service:
  type: NodePort
  port: 5000
  nodePort: null  # Set to a specific port if type is NodePort
mountConfig: false
persistence: false
# zot

Without your own values, zot would get a random NodePort and no persistence – after every Pod restart all charts would be gone. helm show all shows everything at once.

Save your progress? Sign up for free

Drill 3: Look inside with helm pull

Before you give someone else’s chart permissions in your cluster, you fetch it to disk.

# on prod
helm pull zot/zot --version 0.1.134 --untar
tree zot -L 2 -I unittests
head -2 zot/templates/statefulset.yaml zot/templates/deployment.yaml

Expected (abridged):

zot
├── Chart.yaml
├── README.md
├── templates
│   ├── NOTES.txt
│   ├── _helpers.tpl
│   ├── config.yaml
│   ├── configmap.yaml
│   ├── deployment.yaml
│   ├── ...
│   ├── service.yaml
│   ├── serviceaccount.yaml
│   ├── servicemonitor.yaml
│   ├── statefulset.yaml
│   └── tests
└── values.yaml
==> zot/templates/statefulset.yaml <==
{{- if .Values.persistence  -}}
{{- $pvcName := default (printf "%s-pvc" .Release.Name) .Values.pvc.name -}}

==> zot/templates/deployment.yaml <==
{{ if not .Values.persistence }}
apiVersion: apps/v1

One switch, two worlds: with persistence: true the chart renders a StatefulSet with a PVC, otherwise a Deployment. These are exactly the places you read before installing.

Save your progress? Sign up for free

Drill 4: Install with your own values file

# on prod
cat > zot-values.yaml <<'EOF'
# ~/helm/tag01/zot-values.yaml – Stand Tag 01
service:
  type: NodePort
  nodePort: 30500
persistence: true
pvc:
  storage: 2Gi
mountConfig: true
configFiles:
  config.json: |-
    {
      "storage": { "rootDirectory": "/var/lib/registry" },
      "http": { "address": "0.0.0.0", "port": "5000" },
      "log": { "level": "info" }
    }
resources:
  requests: {cpu: 50m, memory: 64Mi}
  limits: {memory: 256Mi}
EOF
helm install zot zot/zot --version 0.1.134 -n zot --create-namespace \
  -f zot-values.yaml
kubectl -n zot rollout status statefulset/zot --timeout=180s
curl -s localhost:30500/v2/_catalog; echo

Expected (abridged):

NAME: zot
LAST DEPLOYED: Fri Nov 20 00:51:43 2026
NAMESPACE: zot
STATUS: deployed
REVISION: 1
DESCRIPTION: Install complete
NOTES:
Get the application URL by running these commands:
  export NODE_PORT=$(kubectl get --namespace zot -o jsonpath="{.spec.ports[0]...
partitioned roll out complete: 1 new pods have been updated...
{"repositories":[]}

The first line of the file is a header comment. Files you create in this book start with one: path plus Stand Tag 01, German for “as of Day 01”. It tells you which day last changed the file. Comments inside files stay German throughout the book, because later chapters edit these files or Helm shows them.

Read the command as a sentence: install as release zot the chart zot/zot in version 0.1.134 into the namespace zot, with the values from the file. Without --version, Helm takes the latest – in scripts you always pin. mountConfig: true is required, otherwise zot ignores the configFiles block.

Save your progress? Sign up for free

Drill 5: Look at the release

# on prod
helm list -A
helm status zot -n zot

Expected (abridged):

NAME             NAMESPACE    REVISION  STATUS    CHART                      APP VERSION
gateway-api-crd  kube-system  1         deployed  gateway-api-crd-1.6.301    v1.6.3
traefik          kube-system  1         deployed  traefik-41.6.101+up41.6.1  v3.7.13
traefik-crd      kube-system  1         deployed  traefik-crd-41.6.101+up... v3.7.1
zot              zot          1         deployed  zot-0.1.134                v2.1.23
NAME: zot
STATUS: deployed
REVISION: 1
RESOURCES:
==> v1/Service
NAME   TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
zot    NodePort   10.43.102.93   <none>        5000:30500/TCP   53s

==> v1/StatefulSet
NAME   READY   AGE
zot    1/1     53s

==> v1/Pod(related)
NAME    READY   STATUS    RESTARTS   AGE
zot-0   1/1     Running   0          53s

In Helm 4, status shows the resources including Pods by itself. Under Helm 3 you needed --show-resources for that – the flag no longer exists in Helm 4.

You read what Helm has stored with helm get:

# on prod
helm get values zot -n zot | head -4
helm get values zot -n zot --all | wc -l
helm get manifest zot -n zot | grep '^kind:'
helm get metadata zot -n zot

Expected (abridged):

USER-SUPPLIED VALUES:
configFiles:
  config.json: |-
    {
130
kind: ServiceAccount
kind: ConfigMap
kind: Service
kind: StatefulSet
NAME: zot
CHART: zot
VERSION: 0.1.134
APP_VERSION: v2.1.23
NAMESPACE: zot
REVISION: 1
STATUS: deployed
DEPLOYED_AT: 2026-11-20T00:51:43Z
APPLY_METHOD: server-side apply

get values shows only your values, --all the merged ones (130 lines). get manifest is what Helm actually sent to the API. APPLY_METHOD: server-side apply is new in Helm 4 – more on that on Day 14.

Save your progress? Sign up for free

Drill 6: Upgrade, history, rollback

What does 0.1.135 bring? Before you upgrade, you compare the default values:

# on prod
diff <(helm show values zot/zot --version 0.1.134) \
  <(helm show values zot/zot --version 0.1.135)
helm upgrade zot zot/zot --version 0.1.135 -n zot -f zot-values.yaml | head -5
helm history zot -n zot

Expected (abridged):

412a413,414
>   # -- Render the `helm test` hooks. Set to false to leave them out of the release.
>   enabled: true
Release "zot" has been upgraded. Happy Helming!
NAME: zot
LAST DEPLOYED: Fri Nov 20 00:52:49 2026
NAMESPACE: zot
STATUS: deployed
REVISION  UPDATED                   STATUS      CHART        DESCRIPTION
1         Fri Nov 20 00:51:43 2026  superseded  zot-0.1.134  Install complete
2         Fri Nov 20 00:52:49 2026  deployed    zot-0.1.135  Upgrade complete

On the upgrade you pass -f zot-values.yaml again. If you left the file out and set some other value instead, Helm would compute only the chart defaults plus that value – zot would lose its NodePort and persistence. Day 3 shows the exact rules.

# on prod
helm rollback zot 1 -n zot
helm history zot -n zot
kubectl -n zot get sts zot -o jsonpath='{.metadata.labels.helm\.sh/chart}{"\n"}'

Expected (abridged):

Rollback was a success! Happy Helming!
REVISION  UPDATED                   STATUS      CHART        DESCRIPTION
1         Fri Nov 20 00:51:43 2026  superseded  zot-0.1.134  Install complete
2         Fri Nov 20 00:52:49 2026  superseded  zot-0.1.135  Upgrade complete
3         Fri Nov 20 00:53:00 2026  deployed    zot-0.1.134  Rollback to 1
zot-0.1.134

Revision 3 has the content of revision 1. Without a number, Helm rolls back to the previous revision – that is, to 2:

# on prod
helm rollback zot -n zot
helm history zot -n zot --max 2

Expected:

Rollback was a success! Happy Helming!
REVISION  UPDATED                   STATUS      CHART        APP VERSION  DESCRIPTION
3         Fri Nov 20 00:53:00 2026  superseded  zot-0.1.134  v2.1.23      Rollback to 1
4         Fri Nov 20 00:53:09 2026  deployed    zot-0.1.135  v2.1.23      Rollback to 2

zot runs with 0.1.135 again. That is the state for the next days.

Save your progress? Sign up for free

Drill 7: Throwaway release and keep-history

helm uninstall deletes the objects and the history. With --keep-history the log stays – and with it the way back.

# on prod
helm install wegwerf zot/zot --version 0.1.135 -n tag01 --create-namespace \
  --set service.type=ClusterIP --set persistence=true --set pvc.storage=1Gi \
  --wait --timeout 3m | grep STATUS
helm uninstall wegwerf -n tag01 --keep-history
helm list -n tag01
kubectl -n tag01 get all,pvc

Expected (abridged):

STATUS: deployed
release "wegwerf" uninstalled
NAME     NAMESPACE  REVISION  UPDATED  STATUS       CHART        APP VERSION
wegwerf  tag01      1         ...      uninstalled  zot-0.1.135  v2.1.23
NAME                                              STATUS   VOLUME          CAPACITY
persistentvolumeclaim/wegwerf-pvc-wegwerf-zot-0   Bound    pvc-4502992e…   1Gi

(wegwerf is German for “throwaway”.) Two things stand out. First: in Helm 4, helm list shows all releases in every status, including uninstalled. The old helm list -a no longer exists; to filter, you use --deployed, --failed or --uninstalled. Second: the PVC stays. It comes from the StatefulSet’s volumeClaimTemplates and does not belong to the release.

# on prod
helm rollback wegwerf 1 -n tag01
helm history wegwerf -n tag01
helm uninstall wegwerf -n tag01
helm history wegwerf -n tag01
kubectl delete namespace tag01

Expected (abridged):

Rollback was a success! Happy Helming!
REVISION  UPDATED                   STATUS       CHART        DESCRIPTION
1         Fri Nov 20 00:53:20 2026  uninstalled  zot-0.1.135  Uninstallation...
2         Fri Nov 20 00:53:53 2026  deployed     zot-0.1.135  Rollback to 1
release "wegwerf" uninstalled
Error: release: not found
namespace "tag01" deleted

A rollback even brings back an uninstalled release – together with the PVC left behind. After the second uninstall without --keep-history it is gone for good. Only deleting the namespace removes the PVC.

Save your progress? Sign up for free

Exercise: Speed Drills

  1. Show only the chart version of the release zot. Target time: 20 s
  2. Show the values you set in revision 1. Target time: 15 s
  3. Read the NodePort from the stored manifest. Target time: 30 s
  4. Check that zot answers on the VM’s IP. Target time: 15 s

Solution

# on prod
helm list -n zot -o json | jq -r '.[0].chart'
helm get values zot -n zot --revision 1 | head -3
helm get manifest zot -n zot | yq 'select(.kind == "Service") | .spec.ports[0].nodePort'
curl -s -o /dev/null -w '%{http_code}\n' 172.16.0.123:30500/v2/

Expected:

zot-0.1.135
USER-SUPPLIED VALUES:
configFiles:
  config.json: |-
30500
200

Save your progress? Sign up for free

Checkpoint

# on prod
helm list -n zot --deployed --short

Expected: zot

# on prod
helm history zot -n zot --max 1 -o json | jq -r '.[0].chart'

Expected: zot-0.1.135

# on prod
curl -s localhost:30500/v2/_catalog

Expected: {"repositories":[]}

# on prod
kubectl -n zot get pvc

Expected: zot-pvc-zot-0 with status Bound and 2Gi.

Challenge

Without installing, find out which Kubernetes objects the zot chart creates with your values file and which without it. Why do two Pods show up that helm get manifest does not show?

Hint: helm template renders locally, without changing the cluster.

Solution

# on prod
cd ~/helm/tag01
helm template zot zot/zot --version 0.1.135 -f zot-values.yaml | grep '^kind:'
helm template zot zot/zot --version 0.1.135 | grep '^kind:'
helm template zot zot/zot --version 0.1.135 -s templates/statefulset.yaml

Expected:

kind: ServiceAccount
kind: ConfigMap
kind: Service
kind: StatefulSet
kind: Pod
kind: Pod
kind: ServiceAccount
kind: Service
kind: Deployment
kind: Pod
kind: Pod
Error: could not find template templates/statefulset.yaml in chart

The two Pods are test hooks from templates/tests/. helm template prints them too, but in the release hooks are stored separately (helm get hooks, Day 11). And: -s on a file that renders empty with the current values ends with could not find template – the file exists, it just produces nothing.

Save your progress? Sign up for free

Interview Note

  • Chart or release? The chart is the package, the release its instance in the cluster. One chart can run as many releases, even in the same namespace, as long as the names differ.
  • What happens on helm install? Load the chart, merge the values, render the templates, validate, send to the API and store the release as a Secret in the namespace.
  • What does helm rollback do? It writes the content of an old revision as a new revision. It does not roll back data in volumes.

Enterprise Note

  • Always pin third-party charts with --version, and before an upgrade compare helm show values of the old and the new version.
  • Do not install charts directly from the internet; mirror them into your own registry and check them there (Days 15, 16).
  • PVCs from volumeClaimTemplates survive helm uninstall. Cleaning up belongs in the runbook – just like deliberately keeping production data.
  • Use --keep-history for releases whose uninstall you may want to undo.