helm: Error: no available release name found

Output of helm version: Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Output of kubectl version: Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:08:19Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.): kubeadm on digital ocean (see https://mherman.org/blog/2018/08/20/setting-up-a-kubernetes-cluster-on-ubuntu )…I think this approach is called bare metal?

So, like mentioned in #3055, I’m getting the error messages Error: no available release name found when I try helm install stable/mysql.

So, I have a brand new installation with kubeadm, and I use helm init, and I tried all the suggestions in #3055, but nothing works. That’s about all I know.

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 19 (4 by maintainers)

Most upvoted comments

I found this artical which helped me to resolve the same situation with minikube and helm setup easily-install-uninstall-helm-on-rbac-kubernetes Delete Tiller

 kubectl -n kube-system delete deployment tiller-deploy
 kubectl delete clusterrolebinding tiller
 kubectl -n kube-system delete serviceaccount tiller

Reinstall with RBAC

 kubectl -n kube-system create serviceaccount tiller
 kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller
 helm init --service-account=tiller

+20

kodelint on Dec 19, 2018

I found this artical which helped me to resolve the same situation with minikube and helm setup easily-install-uninstall-helm-on-rbac-kubernetes Delete Tiller
 kubectl -n kube-system delete deployment tiller-deploy
 kubectl delete clusterrolebinding tiller
 kubectl -n kube-system delete serviceaccount tiller
Reinstall with RBAC
 kubectl -n kube-system create serviceaccount tiller
 kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller
 helm init --service-account=tiller

This worked for me in DigitalOcean.

markserrano915 on Feb 16, 2019

And you initialized tiller via helm init --service-account=tiller? Check the tiller-deploy Deployment object in kube-system and post the YAML output here. 😃

bacongobbler on Aug 21, 2018