jx create cluster makes an incompatible cluster on AKS

Vaccano commented 4 years ago

Summary

jx install part of jx create cluster fails on AKS with

Your current helm version v3 is not supported. Please downgrade to helm v2.

Steps to reproduce the behavior

Browse to https://shell.azure.com/
Start an Azure Cloud Shell connected to an Azure account.
Run jx version. If asked to upgrade select yes. 3a. If you upgraded, change directories to /home/your_user_name_here/.jx/bin 3b. Replace jx with ./jx in all commands below.
Run jx create cluster aks -c KubeJx2
Complete the device login challenge
Wait for the cluster to be created.
When asked for "Jenkins installation type" select "Serverless Jenkins X Pipelines with Tekton" RESULT: The following error is given:

FATAL: Your current helm version v3 is not supported. Please downgrade to helm v2.

NOTE: I also tried these same steps, replacing step 3's command with jx create cluster aks -c KubeJx -- helm3. The result was the same error requesting a downgrade to helm v2.

Expected behavior

When running jx create cluster aks it will create a cluster that is compatible with Jenkins X.

Actual behavior

jx create cluster aks creates a cluster that is incompatible with Jenkins X (uses a version of Helm that it does not support).

Jx version

The output of jx version is:

2.0.1082

Jenkins type

[X ] Serverless Jenkins X Pipelines (Tekton + Prow)
[ ] Classic Jenkins

Kubernetes cluster

AKS Cluster created using jx create cluster

Operating system / Environment

Azure Cloud Shell

Vaccano commented 4 years ago

Is there a work around to this issue?

Some command line parameter that can be passed into jx to make it force AKS to use the older version of Helm maybe?

(I want to evaluate JenkinsX somehow, but can't make a testing system in Azure (where I have cloud computer time))

bitsofinfo commented 4 years ago

same issue here

Labibme commented 4 years ago

i have same issue with advanced version [mini@vlmnk8 ~]$ jx add app jx-app-ui ERROR: Error loading team settings. the server could not find the requested resource (get environments.jenkins.io) WARNING: Failed to retrieve team settings: failed to setup the dev environment for namespace 'default': the server could not find the requested resource (post environments.jenkins.io) - falling back to default settings... FATAL: Your current helm version v3 is not supported. Please downgrade to helm v2. [mini@vlmnk8 ~]$ jx --version 2.1.10

jenkins-x-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

bitsofinfo commented 4 years ago

/remove-lifecycle stale

jenkins-x-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle rotten

bitsofinfo commented 3 years ago

/remove-lifecycle rotten

jenkins-x-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x / jx