chectl server:start on docker-desktop as platform fails by default

[benoitf]

Describe the bug

Installing che with default settings is failing on docker-desktop with the missing che namespace

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

$ chectl server:start --platform=docker-desktop
› Current Kubernetes context: 'docker-desktop'
 ›   Warning: 'server:start' command is deprecated. Use 'server:deploy' instead.
› Installer type is set to: 'operator'
  ✔ Verify Kubernetes API...OK
  ✔ 👀  Looking for an already existing Eclipse Che instance
    ✔ Verify if Eclipse Che is deployed into namespace "che"...it is not
  ✔ ✈️  Docker Desktop preflight checklist
    ✔ Verify if kubectl is installed
    ✔ Verify if kubectl context is Docker Desktop: Found docker-desktop.
    ✔ Verify remote kubernetes status...done.
    ✔ Check Kubernetes version: Found v1.19.3.
    ✔ Verify if nginx ingress is installed
    ✔ Installing nginx ingress
    ✔ Verify domain is set... auto-assigning domain to 10.0.0.244.nip.io....set to 10.0.0.244.nip.io.
  ✔ Start following logs
    ✔ Start following Operator logs...done
    ✔ Start following Eclipse Che logs...done
    ✔ Start following Postgres logs...done
    ✔ Start following Keycloak logs...done
    ✔ Start following Plugin registry logs...done
    ✔ Start following Devfile registry logs...done
  ✔ Start following events
    ✔ Start following namespace events...done
 ›   Warning: Consider using the more reliable 'OLM' installer when deploying a stable release of Eclipse Che (--installer=olm).
  ❯ 🏃‍  Running the Eclipse Che operator
    ✔ Copying operator resources...done.
    ✔ Create Namespace (che)
    ✖ Create ServiceAccount che-operator in namespace che
      → namespaces "che" not found
      Create Role che-operator in namespace che
      Create ClusterRole che-che-operator
      Create RoleBinding che-operator in namespace che
      Create ClusterRoleBinding che-che-operator
      Create CRD checlusters.org.eclipse.che
      Waiting 5 seconds for the new Kubernetes resources to get flushed
      Create deployment che-operator in namespace che
      Operator pod bootstrap
      Prepare Eclipse Che cluster CR
 ›   Error: Error: namespaces "che" not found
 ›   Installation failed, check logs in '/var/folders/tg/_5rxbhmj4xncz4szvpgswrmc0000gn/T/chectl-logs/1605793099170'

Expected behavior

che namespace being automatically created.

If I create the namespace it's working but first experience fails

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

$ docker version
Client: Docker Engine - Community
 Cloud integration: 1.0.2
 Version:           19.03.13
 API version:       1.40
 Go version:        go1.13.15
 Git commit:        4484c46d9d
 Built:             Wed Sep 16 16:58:31 2020
 OS/Arch:           darwin/amd64
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          19.03.13
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       4484c46d9d
  Built:            Wed Sep 16 17:07:04 2020
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          v1.3.7
  GitCommit:        8fba4e9a7d01810a393d5d25a3621dc101981175
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Screenshots

Installation method

• chectl

Environment

   - [x] macOS

[tolusha]

This problem was already mentioned by some user but I don't understand how it is possible.

   ✔ Create Namespace (che)
    ✖ Create ServiceAccount che-operator in namespace che
      → namespaces "che" not found

[tolusha]

I can assume that in Create namespace task we just send a request to create a namespace which requires some time.
It explains why on the next it might fail

[tsmaeder]

Note that doing the exact same command worked for me with docker-desktop on Windows 10.