[SOLVED] Helm Error: no available release name found

[Solved] Helm – Error: no available release name found

When I ran helm install, I got “Error: no available release name found” error. What should I do?

If you get no available release error in helm, it is likely due to the RBAC issue.

While configuring helm, you would have probably created a RBAC with a service account named tiller which binds to a clusterRoleBinding with cluster admin credentials.

Here is how the RBAC file looks like.

However, when you initialize helm, you would have missed to pass the service account with the init command.

Error: no available release name found Resolution

The resolution is pretty simple. You just need to pass the created service account with the init command..

Before you do this delete the existing tiller deployment using the following command.

Make sure the tiller-deploy deployment is deleted using the following command.

Now, re-initialize helm with service account.

Now if you try deploying using helm, you should not be seeing “Error: no available release name found” error.

Related

Rails form_for helper used the active record class for handling the forms and saving to database. However in some cases…

Read more

1. Variables:$ sign is used for defining the variables in PHP. eg:  $var_1 =12. Here the datatype is…

Read more

I assume that you have lamp stack installed in your system. And if you have PHP version lower than 5.1, you have…

Read more
About

The Best Tutorials & Tips to Speedup Your DevOps Workflow.

Created by Bibin Wilson.