What Is Helm? The Package Manager for Kubernetes

Helm is the package manager for Kubernetes - it installs, upgrades, and rolls back applications packaged as charts, the way apt or npm manage packages.

Helm is to Kubernetes what apt is to Debian: a tool for installing and managing packaged applications. The packages are charts; Helm renders a chart with your values, applies the result to the cluster, and tracks it as a versioned release you can upgrade or roll back as a unit.

Helm vs a Helm chart

Helm is the tool (the helm CLI and its logic); a chart is a package it operates on. People say "Helm" loosely for both, but the distinction matters: you run Helm to install a chart.

Releases and lifecycle

Installing a chart creates a named release. Helm records each revision, so helm upgrade, helm rollback, and helm history give you full lifecycle control over the whole app at once, not per-manifest.

Templating with values

Helm renders chart templates with a values file, producing concrete manifests. The same chart serves many environments by supplying different values - the key to clean promotion across environments.

Helm repositories

Charts are shared via chart repositories (and OCI registries).
helm repo add and helm pull fetch published charts.
Public charts exist for many common apps (databases, ingress, monitoring).

Helm in CI/CD

CD pipelines commonly run helm upgrade --install with the new image tag, or commit chart changes for a GitOps controller to apply. Either way Helm packages the deploy into one versioned, rollback-able unit.

Key takeaways

Helm is the package manager; charts are the packages it installs.
Releases give versioned install, upgrade, and rollback of a whole app.
One chart serves many environments via different values files.