Answer by Bibin Wilson for Helm: Error: no available release name found
It's an RBAC issue. You need to have a service account with a cluster-admin role. And you should pass this service account during HELM initialization. For example, if you have created a service account...
View ArticleAnswer by Omar L. for Helm: Error: no available release name found
This solution has worked for me: https://github.com/helm/helm/issues/3055#issuecomment-397296485 $ kubectl create serviceaccount --namespace kube-system tiller $ kubectl create clusterrolebinding...
View ArticleAnswer by suresh Palemoni for Helm: Error: no available release name found
All addons in the kubernetes use the "defaults" service account. So Helm also runs with "default" service account. You should provide permissions to it. Assign rolebindings to it. For read-only...
View ArticleAnswer by robrich for Helm: Error: no available release name found
Per https://github.com/kubernetes/helm/issues/3055 helm init --service-account default This worked for me when the RBAC (serviceaccount) commands didn't.
View ArticleAnswer by Vikram Hosakote for Helm: Error: no available release name found
Per https://github.com/kubernetes/helm/issues/2224#issuecomment-356344286, the following commands resolved the error for me too: kubectl create serviceaccount --namespace kube-system tiller kubectl...
View ArticleAnswer by karthik101 for Helm: Error: no available release name found
The solution given by kujenga from the GitHub issue worked without any other modifications: kubectl create serviceaccount --namespace kube-system tiller kubectl create clusterrolebinding...
View ArticleAnswer by MrMackey for Helm: Error: no available release name found
I had the same issue with the kubeadm setup on to CentOS 7. Helm doesn't make a service account when you "helm init" and the default one doesn't have the permissions to read from the configmaps - so it...
View ArticleAnswer by Simon I for Helm: Error: no available release name found
I think it's an RBAC issue. It seems that helm isn't ready for 1.6.1's RBAC. There is a issue open for this on Helm's Github. https://github.com/kubernetes/helm/issues/2224 "When installing a cluster...
View ArticleHelm: Error: no available release name found
I am getting a couple of errors with Helm that I can not find explanations for elsewhere. The two errors are below. Error: no available release name found Error: the server does not allow access to...
View ArticleAnswer by HiB for Helm: Error: no available release name found
check the logs for your tiller container:kubectl logs tiller-deploy-XXXX --namespace=kube-system if you found something like this: Error: 'dial tcp 10.44.0.16:3000: connect: no route to host'Then...
View Article
