What is a Helm Release and how does Helm manage release state?

A Helm Release is a specific instance of a chart running in a Kubernetes cluster. When you install a chart with a unique release name (e.g., helm install my-nginx bitnami/nginx), Helm creates a release named "my-nginx" that contains all the resources generated from that chart plus metadata about the deployment. This release concept is what enables Helm's powerful lifecycle management features.

Helm v3 manages release state using Kubernetes Secrets stored in the same namespace as the release. Each release creates a secret named sh.helm.release.v1.<release-name>.v<revision-number>. These secrets contain the complete state of the release including all rendered manifests, chart metadata, values used, and status information. The secrets are versioned - each install, upgrade, or rollback creates a new secret revision, allowing Helm to maintain a complete history of changes.

The release management workflow works as follows:

• Install - Creates revision 1 of the release secret with status=deployed
• Upgrade - Creates revision 2 (or higher) with status=deployed
• Rollback - Creates a new revision that reuses manifests from a previous revision
• Uninstall - Marks release as uninstalled (can keep history with --keep-history)