Jx: helm version not compatible with new clusters: UPGRADE FAILED: incompatible versions client[v2.10.0-rc.1] server[v2.9.1]

[michaelneale]

Summary

Running a new cluster from macos will not work due to a helm compatibility issue, not sure if this is related to client on macos (which at latest is 2.9.1) not being server version which seems to be the 2.10 rc).

If you let jx install helm - it will bring the 2.9.1 version, yet 2.10 is used by jenkins x...

Steps to reproduce the behavior

Try installing fresh on macos

Jx version

jx version
NAME VERSION
jx 1.3.100
jenkins x platform 0.0.1827
kubernetes cluster v1.9.7-gke.3
kubectl v1.10.0
helm client v2.9.1+g20adb27
helm server v2.9.1+g20adb27
git git version 2.14.1
The output of jx version is:

This is a lie however, as the error in the environment pipelines built are:

Applying helm chart at . as release name jx-production to namespace jx-production
error: failed to run 'helm upgrade --namespace jx-production --install jx-production .' command in directory '.', output: 'Error: UPGRADE FAILED: incompatible versions client[v2.10.0-rc.1] server[v2.9.1]

not sure where 2.10 is coming from...

Kubernetes cluster

jx create cluster gke

Operating system / Environment

macos

Expected behavior

Actual behavior

[michaelneale]

To fix this - I manually downloaded the RC of helm for macos, the one that jx downloaded was wrong.

[michaelneale]

I expect this should go once jx can download the real final version of 2.10

[merou]

just run this locally:
helm init --upgrade

jx version should then return:
helm client v2.10.0-rc.1+gaa98e7e
helm server v2.10.0-rc.1+gaa98e7e

Tested on AKS.

[jstrachan]

once we've released the new platform, doing a jx upgrade platform should fix this so that we'll auto-upgrade tiller on the fly inside the pipelines if need be

[deyceg]

@jstrachan do you think its right that you're forcing users to use _release candidate_ versions? I'm all for keeping things up to date but the base version should be the current release, which is 2.9.x.

was there a specific reason for the upgrade?

[francesco-beccaria]

@jstrachan I agree with @deyceg
Is there a way to specify which helm version should be used? (eg. via Environment Variable)

[sbadakhc]

@jstrachan @francesco-beccaria I'm also wondering if there is way to specify this. Our builds are breaking because of this.

Thanks,
Sal

[tdcox]

There are some fairly serious stability issues with earlier versions of helm, so it is advisable to update client versions to match those of the build environments.

[mikamboo]

Hello !

I got the same issue... Error: Chart incompatible with Tiller v2.13.0-rc.2

Ouput of helm version :

Client: &version.Version{SemVer:"v2.13.0-rc.2", GitCommit:"b0d4c9eb82e036c52d130fcb031e788dffe5a5dd", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.0-rc.2", GitCommit:"b0d4c9eb82e036c52d130fcb031e788dffe5a5dd", GitTreeState:"clean"}

Any idea ?