Uninstalling Releases
What you'll learn: How to cleanly remove Helm-managed applications from your Kubernetes cluster and understand what happens during cleanup.
After deploying applications with Helm, you'll eventually need to remove them—whether for decommissioning services, cleaning up test environments, or freeing cluster resources. Helm provides a straightforward uninstallation process that removes all resources associated with a release.
The helm uninstall Command
To remove a Helm release, use:
helm uninstall <release-name>
For example, if you installed a release named my-app:
helm uninstall my-app
This command deletes all Kubernetes resources (Deployments, Services, ConfigMaps, etc.) that were created as part of that release.
What Gets Cleaned Up?
By default, helm uninstall removes:
- All Kubernetes objects defined in the chart
- The release metadata from Helm's storage
Think of it like uninstalling software from your computer—the application and its configuration disappear, but some data might remain intentionally (like persistent volumes).
What Doesn't Get Deleted?
Certain resources may persist after uninstallation:
- PersistentVolumes (PVs) with a
Retainreclaim policy stay to prevent accidental data loss - Secrets or ConfigMaps created outside the Helm chart
- Custom Resource Definitions (CRDs) sometimes remain to avoid breaking other applications
Verifying Uninstallation
Check that your release is gone:
helm list
The release should no longer appear in the output.
Key Takeaway: helm uninstall cleanly removes Helm releases and their associated Kubernetes resources, but intentionally preserves certain data-bearing resources like persistent volumes to prevent accidental data loss.