Error: Could Not Find Tiller' When Running 'Helm Version'

`Error: could not find tiller` when running `helm version`

The current helm version does not work with kubernetes version 1.16.0

You can downgrade kubernetes to version 1.15.3

minikube start --kubernetes-version 1.15.3
helm init 

or use my solution to fix it at version 1.16.0

You have to create tiller Service Account and ClusterRoleBinding.

You can simply do that by using those commands:

kubectl --namespace kube-system create sa tiller
kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller

And simply create tiller

helm init --override spec.selector.matchLabels.'name'='tiller',spec.selector.matchLabels.'app'='helm' --output yaml | sed 's@apiVersion: extensions/v1beta1@apiVersion: apps/v1@' | kubectl apply -f -

helm upgrade: Error: could not find a ready tiller pod

If you specify the --client-only flag, the tiller server is never started in the cluster. Hence your problem. You can remove the flag and it should work.

See the docs for more details.

Update: Based on the output of helm version --tls and the discussion in comments, we can see that the tiller service is not working and pods are stuck in IMAGE_PULL_BACKOFF. Fixing that will fix this issue.

The tiller pods can no longer pull images since the upstream registry has been decommissioned. The image name can be changed to omio/gcr.io.kubernetes-helm.tiller:v2.16.1. This is a working registry for helm v2.

Install helm 2.13.0 on Minikube server (1.6.2) could not find tiller

This can be fixed by deleting the tiller deployment and service and rerunning the helm init --override command after first helm init.

So after running commands You listed:

$ kubectl -n kube-system create serviceaccount tiller
serviceaccount/tiller created

$ kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount kube-system:tiller
clusterrolebinding.rbac.authorization.k8s.io/tiller created

$ helm init --service-account tiller

And then finding out that tiller could not be found.

$ helm version
Client: &version.Version{SemVer:"v2.13.0", GitCommit:"79d07943b03aea2b76c12644b4b54733bc5958d6", GitTreeState:"clean"}
Error: could not find tiller

Run the following commands:

1.

$ kubectl delete service tiller-deploy -n kube-system

2.

$ kubectl delete deployment tiller-deploy -n kube-system

3.

helm init --override spec.selector.matchLabels.'name'='tiller',spec.selector.matchLabels.'app'='helm' --output yaml | sed 's@apiVersion: extensions/v1beta1@apiVersion: apps/v1@' | kubectl apply -f -

---

After that You can verify if it worked with:

$ helm version
Client: &version.Version{SemVer:"v2.13.0", GitCommit:"79d07943b03aea2b76c12644b4b54733bc5958d6", GitTreeState:"clean"}
Error: could not find a ready tiller pod

This one needs little more time, give it few seconds.

$ helm version
Client: &version.Version{SemVer:"v2.13.0", GitCommit:"79d07943b03aea2b76c12644b4b54733bc5958d6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.0", GitCommit:"79d07943b03aea2b76c12644b4b54733bc5958d6", GitTreeState:"clean"}

Tell me if it worked.

Error: error installing: the server could not find the requested resource HELM Kubernetes

I met the same problem, then I found this reply on here.

helm init --service-account tiller --override spec.selector.matchLabels.'name'='tiller',spec.selector.matchLabels.'app'='helm' --output yaml | sed 's@apiVersion: extensions/v1beta1@apiVersion: apps/v1@' | kubectl apply -f -

It works for me. You can see the detail in this issue.

---

Related Topics