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

helm version is outdated, does not work on k8s 1.16.x #792

Closed
vroad opened this issue Nov 11, 2019 · 1 comment · Fixed by #793
Closed

helm version is outdated, does not work on k8s 1.16.x #792

vroad opened this issue Nov 11, 2019 · 1 comment · Fixed by #793

Comments

@vroad
Copy link

vroad commented Nov 11, 2019

Is your feature request related to a problem?
Yes.
I can't directly use helm CLI from command line, because helm won't connect to older tiller.

Error: incompatible versions client[v2.16.0] server[v2.13.1]

Also, older version of helm does not work on k8s v1.16.x. Recently, helm 2.16.0 was released, which adds support for k8s 1.16.x.

https://github.com/helm/helm/releases/tag/v2.16.0

I can't find any documentation on which version of k8s devspace currently supports. Is this currently documented?

Desvspace currently uses 2.13.1, which was released at Mar 22: https://github.com/helm/helm/releases/tag/v2.13.1

Which solution do you suggest?
Upgrade helm version that devspace is currently using.
And/or make helm version configurable, but is that possible?

I can't seem to prevent devspace from deploying tiller and install one by myself.

Which alternative solutions exist?
Use older helm client to avoid errors, but this does not solve the problem of k8s v1.16.x support.

Additional context
It's possible to run tiller 2.16.0 on k8s 1.15.x cluster as well.

/kind feature

@FabianKramm
Copy link
Collaborator

FabianKramm commented Nov 11, 2019

@vroad thanks for opening this issue. Actually we use internally helm version 2.15, but still deploy an older tiller (good catch). I will fix that in the upcoming release and update helm to 2.16

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

Successfully merging a pull request may close this issue.

2 participants