Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

microk8s.helm returns Eror: could not find tiller #695

Closed
davidthewatson opened this issue Oct 1, 2019 · 10 comments
Closed

microk8s.helm returns Eror: could not find tiller #695

davidthewatson opened this issue Oct 1, 2019 · 10 comments

Comments

@davidthewatson
Copy link

@davidthewatson davidthewatson commented Oct 1, 2019

I've installed microk8s on ubuntu 19.04 with:

snap install microk8s --classic --edge

I then enable helm:

microk8s.enable helm

which produces:

Enabling Helm
Helm is enabled

I then issue:

microk8s.helm version

which produces:

Client: &version.Version{SemVer:"v2.14.3",     GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085",  GitTreeState:"clean"}
Error: could not find tiller

For some reason, tiller does not install properly on v2.14.3.

inspection-report-20191001_135328.tar.gz

@balchua
Copy link
Collaborator

@balchua balchua commented Oct 1, 2019

Enabling helm in microk8s does not explicitly install tiller.

Also Kubernetes 1.16 disabled the deprecated apis. I think we'll have to update the helm version bundled as soon as 2.15.0 is ready.

helm/helm#6374

@davidthewatson
Copy link
Author

@davidthewatson davidthewatson commented Oct 2, 2019

Sorry about that. Here's the additional detail that I forgot:

$ microk8s.helm init
$HELM_HOME has been configured at /home/watson/.helm.
Error: error installing: the server could not find the requested resource

Of course, this is after the helm enable.

@balchua
Copy link
Collaborator

@balchua balchua commented Oct 2, 2019

@davidthewatson yeah that's due to the disabled api in kubernetes 1.16.
Thanks

@ktsakalozos
Copy link
Member

@ktsakalozos ktsakalozos commented Oct 3, 2019

While we wait for a helm release [1] we can:

  • use MicroK8s v1.15 with sudo snap install microk8s --classic --channel=1.15/stable
  • go through the issue [2] and try any workarounds described there.

Apologies for any inconvenience.

[1] https://github.com/helm/helm/releases
[2] helm/helm#6374

Related to:
#70 (comment)

@andrewfinnell
Copy link

@andrewfinnell andrewfinnell commented Oct 5, 2019

The following command worked quite well for me

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

@jon-dearaujo
Copy link

@jon-dearaujo jon-dearaujo commented Oct 16, 2019

The following command worked quite well for me

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

This allows the creation of Tiller's deployment and service but when I tried microk8s.helm version again I got the same Error: cannot connect to Tiller.

@balchua
Copy link
Collaborator

@balchua balchua commented Nov 1, 2019

This can be closed now. Helm 2.15.1 is now merged.
@ktsakalozos

@ktsakalozos
Copy link
Member

@ktsakalozos ktsakalozos commented Nov 2, 2019

Indeed, the latest helm is on edge and should reach stable with the next patch release (1.16.3)

@zbyte64
Copy link

@zbyte64 zbyte64 commented Mar 11, 2020

Having this issue, fresh install today:

~$ microk8s.helm version
Client: &version.Version{SemVer:"v2.16.0", GitCommit:"e13bc94621d4ef666270cfbe734aaabf342a49bb", GitTreeState:"clean"}
Error: could not find tiller

@balchua
Copy link
Collaborator

@balchua balchua commented Mar 12, 2020

@zbyte64 can you check tiller pod? Also after enabling helm, did you run microk8s.helm init?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants