You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice if we can figure out a way to auto-install the latest 2.14 release in this case so new installs do not break, perhaps by downloading the binary ourselves like it is done with kubectl?
I have the same issue OSX with in a minikube environment, is there a work around for this issue?
You can simply install Helm 2.14.3 yourself and put it into your search path, e.g. by downloading their GitHub release directly: https://github.com/helm/helm/releases/tag/v2.14.3
Then jx boot will use that one and won't offer to to install it from another source.
Changing jx boot so that it downloads this specific Helm release this way would fix this issue.
Reproduced on Ubuntu 18. jx boot downloads a version of helm that is too new (2.16) to use on subsequent runs.
Worked around by manual install of helm 2.14.3 as above, but not particularly ideal.
Summary
When using
jx boot
on a fresh GKE cluster I get this error:Steps to reproduce the behavior
jx create cluster gke
(probably also happens with other clusters)helm
jx boot
if you used--skip-installation
at the cluster creation command.Expected behavior
Helm works as expected
Actual behavior
It is reported that the Helm version is too new.
I suspect this happens because the
kubernetes-helm
brew package is quite new, and this now breaks fresh installations.Jx version
v2.0.941 on macOS installed through Homebrew.
jx version
not yet available because Jenkins X is not yet installed in cluster.Jenkins type
Not chosen, Jenkins X is not yet installed in cluster.
Kubernetes cluster
GKE, using
jx create cluster gke
commandOperating system / Environment
macOS 10.14.6
The text was updated successfully, but these errors were encountered: