jx create cluster gke --ng fails with missing ingress-config

[ascheman]

Summary

Cannot setup a JX cluster on GKE with Next Generation CLI option.

Steps to reproduce the behavior

: ${JX_GIT_USER:="ascheman"}
: ${JX:="jx"}
# TODO filter for username
: ${JX_GIT_APITOKEN:=`yq r ~/.jx_gke/gitAuth.yaml servers[0].users[0].apitoken`}

export JX_GIT_USER JX_GIT_APITOKEN

: ${JX_HOME:="$HOME/.jx_gke"}
: ${JX_NAME:="jx-gke-`date +%y%m%d-%H%M`"}
: ${JX_GKE_PROJECT:="jxtest-199909"}
: ${KUBECONFIG:="${JX_HOME}/kubeconfig"}

export JX_HOME JX_NAME JX_GKE_PROJECT KUBECONFIG

jx create cluster gke \
    -n ${JX_NAME} \
    -z us-east1-b \
    -m n1-standard-4 \
    -p ${JX_GKE_PROJECT} \
    --min-num-nodes=3 \
    --max-num-nodes=5 \
    --environment-git-owner=${JX_GIT_USER} \
    --git-api-token=${JX_GIT_APITOKEN} \
    --git-username=${JX_GIT_USER} \
    --skip-login=true \
    \
    --preemptible=true \
    \
    --exposer='Ingress' \
    --kaniko=true \
    \
    --ng=true \
    \
    --kubernetes-version=1.12.7-gke.10

Expected behavior

New cluster with JX up and running!

Actual behavior

JX installation failed with "ingress-config" not found

...
Creating service account jxkaniko-jx-gke-190502-1507
Assigning role roles/storage.admin
Assigning role roles/storage.objectAdmin
Assigning role roles/storage.objectCreator
Downloading service account key
No default password set, generating a random one
Setting the dev namespace to: jx
Generated helm values /Users/ascheman/.jx_gke/extraValues.yaml
Installing Jenkins X platform helm chart from: /Users/ascheman/.jx_gke/cloud-environments/env-gke
Configuring the TeamSettings for Prow with engine Tekton
Setting the current namespace to: jx
ERROR: error creating cluster configuring and installing Prow: installing Prow: configmaps "ingress-config" not found
error: configuring and installing Prow: installing Prow: configmaps "ingress-config" not found

Jx version

The output of jx version is:

WARNING: Failed to find helm installs: running helm list --all --namespace : failed to run 'helm list --all --namespace ' command in directory '', output: 'Error: could not find tiller' WARNING: Failed to get helm version: failed to run 'helm version --short' command in directory '', output: 'Client: v2.13.1+g618447c Error: could not find tiller' NAME VERSION jx 2.0.72 Kubernetes cluster v1.12.7-gke.10 kubectl v1.14.1 git git version 2.21.0 Operating System Mac OS X 10.14.4 build 18E226

Jenkins type

• [x] Next Generation (Tekton + Prow)
• [ ] Classic Jenkins
• [ ] Serverless Jenkins (JenkinsFileRunner + Prow)

[ascheman]

Retried this today with eh current JX CLI

NAME               VERSION
jx                 2.0.82
Kubernetes cluster v1.12.7-gke.10
kubectl            v1.14.1
git                git version 2.21.0
Operating System   Mac OS X 10.14.4 build 18E226

but without

    --exposer='Ingress' \
    --kaniko=true \

and still see the same error.

If I check for the configmaps, the CM ingress-config is available in namespace jx.

[ascheman]

If I use --tekton=true instead of --ng=true a new cluster is set up and seems to be working.

[doc-olliday]

Same problem here when installing jx on minikube.

[jenkins-x-bot]

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]

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

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.