Hands-on Lab·Certified Kubernetes Administrator
Helm Basics
Helm templates YAML and remembers what it sent, which is what makes rollback work. The corollary catches everyone: a change you make with kubectl is invisible to Helm and gets reverted by the next upgrade.
Cluster Architecture and Configuration Guide 18 of 103 Intermediate
- Kubernetes1.36.4
- Helmv3.18.5
- Cluster4 nodes
- TimeAbout 40 min
- Reviewed21 August 2026
Written against the versions above. Helm 3. Helm 2 needed a cluster-side Tiller component and is long dead; anything referring to Tiller is out of date.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA1001 | 192.168.0.175 | Ubuntu 26.04 LTS | Control Plane Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE01 | 192.168.0.176 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE02 | 192.168.0.177 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE03 | 192.168.0.178 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
Before you start
- The Deployments and Services guides.
- A working kubeconfig, since Helm uses the same credentials
kubectldoes. - Outbound internet access to add a chart repository.
-
A client-side binary, and nothing in the cluster
-
A chart is a directory with a contract
-
Render locally before touching the cluster
-
Repositories, and reading a chart before trusting it
-
Install, and where the release actually lives
-
What was sent, and what changed
-
Upgrade, history, rollback, and the change that vanishes
-
Uninstall, and the two things it leaves behind