Helm "INSTALLATION FAILED" - Fix Failed Installs in CI

INSTALLATION FAILED is Helm’s wrapper for a failed first install. The common cases are a release name already in use, a resource that already exists, an invalid manifest, or a failed install hook.

What this error means

helm install (or helm upgrade --install on a new release) exits with Error: INSTALLATION FAILED: <reason>. A failed install may leave the release in failed/pending-install.

helm output

Error: INSTALLATION FAILED: cannot re-use a name that is still in use

Common causes

Release name already in use

A prior install (possibly a failed/uninstalled one with leftover state) still holds the name. Helm refuses to reuse a name with an existing release record.

Existing resource or invalid manifest

A rendered object already exists unmanaged, or a manifest fails validation, aborting the install.

How to fix it

Use upgrade --install for idempotent deploys

In CI, upgrade --install installs if absent and upgrades if present, avoiding name-reuse failures on re-runs.

Terminal

helm upgrade --install <release> ./chart -n <ns> --create-namespace

Clear a stuck failed install

Inspect with helm list -a -n <ns> and helm status <release> -n <ns>.
If the release is failed/abandoned, helm uninstall <release> -n <ns> then re-install.
If a specific resource already exists, adopt or remove it (see the resource-already-exists fix).

How to prevent it

Standardize on helm upgrade --install so re-runs are idempotent.
Use --atomic so a failed first install cleans up after itself.
Keep release names stable and unique per environment.