A Release Is an Installed Chart

Think of the chart as a blueprint and the release as the house built from it. Many releases can come from one chart.

Each release name must be unique within its namespace. That name is how you later upgrade, inspect, or uninstall it.

A release belongs to one Kubernetes namespace. The same release name can be reused in a different namespace without clashing.

Run helm list to see the releases in your current namespace, each with its chart, revision, and status.

Helm 3 stores each release's data in a Kubernetes Secret inside the namespace. No external server is needed to track it.

Use helm status with the release name to see its current state and the rendered notes for that running instance.

A release remembers the values you supplied at install. Helm uses them again on upgrade unless you override them.

When you no longer need it, helm uninstall deletes the release and the cluster resources it created.

Separating chart from release lets you manage each deployment independently, even when they share the same underlying chart. 🎯

Installing a chart creates a release: a uniquely named instance in a namespace that you can list, upgrade, and uninstall. ✅