Introduction to Helm

Overview

Explain what Helm solves for Kubernetes teams and define chart, release, and repository in ops language.

Helm is the package manager for Kubernetes. A chart is a versioned bundle of templates and defaults; a release is an installed instance. This course is Helm for Kubernetes Engineers — production charts, not toy demos.

This is a core tutorial in Module 1 · Helm Fundamentals of the REBASH Academy Helm for Kubernetes Engineers series — written for Cloud, DevOps, Platform, and SRE engineers.

Prerequisites

• Kubernetes — Deployments, Services, kubectl apply basics

Learning Objectives

By the end of this tutorial, you will be able to:

• State problems Helm solves vs raw YAML
• Define chart, release, repository
• Contrast imperative apply vs packaged releases
• Name when not to use Helm

Architecture

This topic’s control points and relationships are shown below.

Theory

What it is

Helm is the de facto package manager for Kubernetes. Instead of applying loose YAML files by hand, you install a chart — a versioned directory (or .tgz archive) that contains templates, default values, and metadata. An installed instance of a chart is a release: a named deployment in a namespace with history you can upgrade or roll back. Charts are published from repositories (classic HTTP indexes) or OCI registries (container-style references such as oci://…).

Three words you will use every day:

Term	Meaning
Chart	Packaged templates + values.yaml + Chart.yaml
Release	One installed instance of a chart (name + namespace + revisions)
Repository / OCI	Where teams discover and pull charts

Why it matters

Raw kubectl apply works for a single environment. It breaks down when you need the same app shape in dev, staging, and production with different replicas, images, and ingress hosts. Helm gives you parameterisation (values), a shared package teams can reuse, and release history for rollback. Platform teams publish “golden” charts so product squads do not reinvent Deployments and Services. In GitOps workflows, controllers such as Argo CD and Flux treat Helm charts as first-class deployable units.

How it works

You (or CI/GitOps) run the Helm CLI against a cluster kubeconfig. Helm fetches the chart, merges default values with your overrides, renders Go templates into plain Kubernetes manifests, and applies them through the API server. Helm 3 stores release metadata in the cluster (Secrets or ConfigMaps in the release namespace). Each upgrade creates a new revision; helm rollback re-applies an earlier revision’s rendered set.

Key concepts and comparisons

Pain without Helm	Helm answer
Copy-paste YAML per env	Values overrides (-f, --set)
No versioned app package	Chart version + informational appVersion
Manual rollback	helm rollback or GitOps revert of values/chart
Hard to share standards	Reusable application charts and library charts

Helm vs Kustomize vs plain YAML: use plain YAML or Kustomize when a small, mostly static set of manifests is enough. Prefer Helm when you need rich parameterisation, dependency composition, and release lifecycle across many environments.

Common pitfalls

• Helm is not a second control plane — Kubernetes still owns Pods and Deployments after apply.
• A chart is not a running app; the release is what you operate day to day.
• Helm does not replace GitOps; production teams usually let a controller run Helm, not laptops.
• Over-templating every field makes charts unreadable — keep defaults sensible and overrides intentional.

Hands-on Lab

Create a workspace for this tutorial.

mkdir -p ~/rebash-helm/module-01 && cd ~/rebash-helm/module-01

Focus: Create a chart and install it into namespace rebash-helm

Step 1 – Scaffold and lint a chart

kubectl create namespace rebash-helm
helm create hello-helm
helm lint hello-helm
helm template demo ./hello-helm -n rebash-helm | head -n 40

Step 2 – Install and verify the release

helm upgrade --install demo ./hello-helm -n rebash-helm
helm -n rebash-helm list
kubectl -n rebash-helm get deploy,svc

Final step – Cleanup note

helm uninstall demo -n rebash-helm --ignore-not-found || true
kubectl delete namespace rebash-helm --ignore-not-found
# Workspace kept for notes; remove with: rm -rf "$(pwd)" when finished

Validation

• Lab commands run under ~/rebash-helm/module-01/
• You can explain each Theory section in your own words
• You used modern tooling where it applies to this topic
• You can describe one production failure mode for this topic

Code Walkthrough

Production practice for Introduction to Helm always combines:

1. Inspect before you change (status, plan, logs, dry-run)
2. Prefer reversible, documented changes (Git, IaC, drop-ins, version pins)
3. Capture evidence (command output, pipeline logs) for handovers
4. Prefer current tools and APIs over legacy shortcuts
5. Least privilege — escalate credentials only when required

Keep runbooks short enough to follow under pressure. Automate checks; keep humans for judgement.

Security Considerations

• Treat credentials and tokens for helm as privileged — never commit them
• Prefer short-lived auth (OIDC, roles, SSO) over long-lived keys
• Validate blast radius before apply/deploy/delete operations
• Restrict who can approve production changes
• Collect audit logs; limit who can read sensitive traces

Common Mistakes

Helm is not a second control plane — Kubernetes still owns Pods and Deployments after appl

Validate assumptions against the Theory section and official docs before changing production.

A chart is not a running app; the release is what you operate day to day.

Lab shortcuts (open security groups, admin roles, skip approvals) must not ship unchanged.

Changing production without a rollback path

Always know how to revert (previous artefact, prior release, state rollback, DNS failback).

Best Practices

• Encode Introduction to Helm changes as code and review them in pull requests
• Pin versions (images, modules, actions, provider plugins)
• Separate environments with clear promotion gates
• Alert on symptoms with runbooks attached
• Destroy lab resources; tag everything with owner and expiry where possible

Troubleshooting

Symptom	Likely cause	Fix
Auth / permission denied	Wrong identity, policy, or scope	Check caller identity, roles, and least-privilege policies
Timeout / no route	Network, DNS, security group, or endpoint	Trace path, DNS, and allow-lists before retrying
Drift / unexpected plan	Manual change or wrong state/workspace	Reconcile desired vs actual; avoid click-ops on managed resources
Pipeline/job red	Flaky step, cache, or missing secret	Read failing step logs; bisect recent workflow/config changes
Cost spike	Idle load balancer, NAT, oversized compute	Inventory billable resources; stop/delete labs promptly

Summary

Introduction to Helm is essential for Cloud and DevOps engineers working with helm. Practise the lab until the inspection and change path is muscle memory, then continue the track.

Interview Questions

1. What problem does Helm solve for Kubernetes packaging?
2. What is a release in Helm 3?
3. How do charts differ from raw manifests?
4. What risks come from installing untrusted charts?
5. What is the difference between helm template and helm install?

Sample answer — question 2

A release is a named instance of a chart running in a cluster (with revision history). Helm tracks it via release metadata stored as Secrets (or ConfigMaps) in the namespace.

Sample answer — question 4

Untrusted charts can create privileged workloads, ClusterRoles, or exfiltrate secrets. Always render and review, pin versions, and install into least-privilege namespaces.

Related Tutorials

• Course overview
• Helm Architecture and Components

References

• Helm docs — introduction