INSTALLATION FAILED: cannot re-use a name that is still in use
Routes helm release-name collisions. Use when helm install fails with cannot re-use a name that is still in use. Not for failed releases blocking upgrade (different error) or namespace confusion.
helm install only creates - it will not adopt or overwrite an existing release, and release names are unique per namespace. You re-ran install for a name that is already there. Use helm upgrade [release] [chart] to change the existing release, or helm uninstall [release] first to start over. In CI, helm upgrade --install makes the step idempotent.
The error
Error: INSTALLATION FAILED: cannot re-use a name that is still in useWhat to do
- See the existing release:
helm list -n [namespace]Expected: Shows the release with the same name.
- To update it:
helm upgrade [release] [chart] -n [namespace] Expected: Prints Release "[release]" has been upgraded.
- To start over:
helm uninstall [release] -n [namespace]then install again. Expected: Prints release "[release]" uninstalled, then install succeeds.
- CI fix: switch the step to
helm upgrade --install [release] [chart]
Expected: First run installs, later runs upgrade, no error.
When this applies
- the exact cannot re-use a name that is still in use message
- deploy pipelines that run helm install on every release
- re-running a tutorial install twice
When it does NOT apply
- UPGRADE FAILED errors (release exists but the operation failed)
- name collisions across namespaces (names are per-namespace, so that works)
Works with
helm 3.x
Error: INSTALLATION FAILED: cannot re-use a name that is still in use (in another namespace)
Names are unique per namespace, so this only happens within one namespace. Check -n / --namespace.
Why it happens
Helm tracks releases as secrets in the namespace; install refuses to touch an existing release record to avoid silently adopting someone else's release.
Edge cases
- A release stuck in pending-install also blocks the name - uninstall it before reinstalling.
- helm list -a shows failed and pending releases that helm list hides.
Resolved from
gh:opscanopy/opscanopy.com (mission90 day-075) - https://github.com/opscanopy/opscanopy.com/blob/HEAD/src/content/mission90/day-075.md
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.