Helm Basics

Cluster Architecture and Configuration / Guide 18 of 103 / Intermediate

• Kubernetes1.36.4
• Cluster4 nodes
• Runtimecontainerd 2.2.6
• CNICalico v3.32.1
• TimeAbout 40 min

Helm 3. Helm 2 needed a cluster-side Tiller component and is long dead; anything referring to Tiller is out of date.

• Helmv3.18.5

This guide includes

Use this when an application has to be packaged, parameterised and upgraded repeatedly. This matters because Helm remembers what it sent, and that record is the only reason helm rollback can work at all.

• confirming Helm 3 is one client-side binary with nothing installed into the cluster
• scaffolding a chart, and rendering it locally with helm template before touching a cluster
• adding a repository and reading a chart before trusting it
• installing a named release, then answering what was sent and what changed with helm get values and get manifest
• upgrading, rolling back and uninstalling - including the hand-made change that vanishes and the two things left behind

Before you start

• The Deployments and Services guides.
• A working kubeconfig, since Helm uses the same credentials kubectl does.
• Outbound internet access to add a chart repository.

1. 1

   A client-side binary, and nothing in the cluster

2. 2

   A chart is a directory with a contract

3. 3

   Render locally before touching the cluster

4. 4

   Repositories, and reading a chart before trusting it

5. 5

   Install, and where the release actually lives

6. 6

   What was sent, and what changed

7. 7

   Upgrade, history, rollback, and the change that vanishes

8. 8

   Uninstall, and the two things it leaves behind

Official sources

• Helm documentation
• Charts
• Helm architecture
• Custom resource definitions in charts
• Recommended labels