Helm "has no deployed releases" - Fix Failed-First-Install Upgrades

Helm can only upgrade a release that has at least one successfully deployed revision. If the first install failed, every revision is in failed state, so helm upgrade errors that the release "has no deployed releases".

What this error means

helm upgrade --install fails with Error: UPGRADE FAILED: "<release>" has no deployed releases. helm history shows only failed revisions and never a deployed one.

helm output

Error: UPGRADE FAILED: "api" has no deployed releases

Common causes

The first install failed

The initial install errored (bad manifest, failed hook, readiness timeout) and left the release with only failed revisions, so there is no deployed base to upgrade from.

Repeated failed upgrades with no good revision

A release that never reached deployed keeps failing each upgrade attempt, because Helm has nothing successful to patch against.

How to fix it

Uninstall the failed release, then reinstall

With no deployed revision to keep, removing the failed release and re-installing cleanly is the reliable path.

Terminal

helm history api -n <ns>
helm uninstall api -n <ns>
helm install api ./chart -n <ns>   # or upgrade --install

Make installs self-healing going forward

Use --atomic so a failed first install rolls back/cleans up instead of leaving a failed release.
Fix the underlying install failure (manifest, hook, or readiness) before retrying.
On older Helm, helm upgrade --install --force can sometimes recover, but uninstall+install is cleaner.

How to prevent it

Use helm upgrade --install --atomic so failed first installs clean up.
Validate the chart (helm template/lint/dry-run) before the first install.
Fix the first-install failure rather than retrying upgrades against a failed release.