Helm: could not find tiller

Question

I'm getting this error message:

➜  ~ helm version Error: could not find tiller 

I've created tiller project:

➜  ~ oc new-project tiller Now using project "tiller" on server "https://192.168.99.100:8443". 

Then, I've created tiller into tiller namespace:

➜  ~ helm init --tiller-namespace tiller $HELM_HOME has been configured at /home/jcabre/.helm.  Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.  Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy. To prevent this, run `helm init` with the --tiller-tls-verify flag. For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation Happy Helming! 

So, after that, I've been waiting for tiller pod is ready.

➜  ~ oc get pod -w NAME                             READY     STATUS    RESTARTS   AGE tiller-deploy-66cccbf9cd-84swm   0/1       Running   0          18s NAME                             READY     STATUS    RESTARTS   AGE tiller-deploy-66cccbf9cd-84swm   1/1       Running   0          24s ^C%                

Any ideas?

Answer 1

Try deleting your cluster tiller

kubectl get all --all-namespaces | grep tiller kubectl delete deployment tiller-deploy -n kube-system kubectl delete service tiller-deploy -n kube-system kubectl get all --all-namespaces | grep tiller 

Initialise it again:

helm init 

Now add the service account:

kubectl create serviceaccount --namespace kube-system tiller kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}' 

This solved my issue!

Answer 2

You don't have helm configured yet, use the following command:

helm init 

This will create .helm with repository, plugins, etc, in your home directory.

Background: helm comes with client and server, if you have a different deployment environment, it might be possible that your helm server (known as tiller) is different, in that case, there are two ways to point to tiller

• set environment variable TILLER_NAMESPACE
• --tiller-namespace string namespace of Tiller (default "kube-system")

For more details check the helm READ.md file.