helm uninstall: Usage, Options & Common CI Errors

Remove a release and everything it created.

helm uninstall deletes a release and the Kubernetes objects it manages. In CI it tears down preview environments and test releases - where idempotency on re-run matters.

What it does

helm uninstall NAME removes the release's resources and its release record. --keep-history retains the revision history (so the release can be rolled back / reinstalled), while the default purges it. --wait blocks until the resources are actually deleted. It does not delete the namespace.

Common usage

Terminal

helm uninstall web -n prod
helm uninstall web --keep-history
helm uninstall web --wait --timeout 2m
helm uninstall web --ignore-not-found        # idempotent in CI

Common errors in CI

"Error: uninstall: Release not loaded: web: release: not found" is the re-run failure - the release was already removed. Use --ignore-not-found so teardown is idempotent. uninstall does not remove the namespace or any PersistentVolumeClaims the chart's StatefulSets created (those are retained by design), so a "clean" environment can keep growing PVCs; delete the namespace explicitly if you need a full wipe. With --keep-history the release name stays reserved, so a later helm install of the same name can hit "cannot re-use a name". Use upgrade --install instead.

Related guides

kubectl Cheat Sheet: Commands for Everyday KubernetesA kubectl cheat sheet - get, describe, logs, apply, rollout, debug, and context commands for daily Kubernetes… helm install: Usage, Options & Common CI Errorshelm install deploys a chart as a new release. Setting values, --wait and --atomic for CI, --dry-run, and the… Helm "cannot re-use a name that is still in use" vs "no deployed releases" in CIFix Helm installs blocked by a prior release stuck in a failed/uninstalling state in CI - "Error: INSTALLATIO… helm list: Usage, Options & Common CI Errorshelm list shows releases and their status. All-namespaces, status filters, output formats for scripting, and…