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

user_9536168 0
Viewed 6699

I have deployed a helm chart as shown below:

enter image description here

When I try to run the helm upgrade command, I get the following error:

enter image description here

I tried using the --force option too but still the same.

How can I rectify this error?

kubernetes-helm kubernetes
4 Answers

For helm3, helm uninstall --namespace $NAMESPACE $RELEASE_NAME

user_76343740

Helm v3.7.2

helm upgrade --install

-i, --install if a release by this name doesn't already exist, run an install

user_4910660

In my case, this issue pop up, when I had 10+ failed releases. I had to manually delete / patch release secrets.

This is however fixed for version 3.9.0.

TL;DR

use Helm 3.9.0+

user_12761230

As per this website:

Helm 2 compares the current deployment manifest with the new one to apply the necessary patches. It does not, however, compare the state of the resources between the manifests. If a previous deployment failed, it is likely that the cluster has some missing resources. Prior to Helm 2.7.1, Helm will try to upgrade the deployment without installing the missing resources. To prevent this, as of version 2.7.1, Helm uses the latest successful deployment as the baseline for the upgrade. If there is no successful deployment to be found, the system returns the “helm has no deployed releases” error message.

so you can try to follow the solutions 1 and 3 mentioned there since you've tried to use the --force flag already.

user_160257110
Related