Implement a single host version of the happy-path test

[l0rd]

Is your task related to a problem? Please describe.

Single host is not currently tested.

Describe the solution you'd like

Implement an happy path tests to address that.

cc @dmytro-ndp @rhopp

[l0rd]

That's important considered #16702 and #12914

[rhopp]

@l0rd Should single host already work also for Openshift, or is it still just a k8s (ingress) thing? (Asking to beter understand a scope of this)

Also... If we would have to make a decision which "version" (single vs multi host) should be the "primary" target for our testing - is it safe to assume, that single-host will be the more important (in the near future)?

[l0rd]

@rhopp it only works on Kubernetes right now. We are working on #16702 and openshift/origin#20474 to have support on OpenShift routes as well.

[l0rd]

Also... If we would have to make a decision which "version" (single vs multi host) should be the "primary" target for our testing - is it safe to assume, that single-host will be the more important (in the near future)?

Yes

[rhopp]

I've created "subtask" for switching k8s based tests/jobs to single-host: #16904

[sparkoo]

as of today, gateway single-host che-server part is merged in master and is in nightly images at quay.io/eclipse/che-server:nightly. We're working on the che-operator. There is "working" testing image quay.io/lkrejci/che-operator:gateway.

to deploy gateway single-host, use this CheCluster patch:

apiVersion: org.eclipse.che/v1
kind: CheCluster
metadata:
  name: eclipse-che
spec:
  server:
    serverExposureStrategy: 'single-host'
    singleHostExposureType: 'gateway'
    customCheProperties:
      CHE_INFRA_KUBERNETES_SINGLEHOST_WORKSPACE_EXPOSURE: 'gateway'

with this chectl command (don't forget to set <platform>):

chectl server:start --installer=operator --platform=<platform> --che-operator-image=quay.io/lkrejci/che-operator:gateway --che-operator-cr-patch-yaml=op.patch

There are these known limitations/WIP:

• the extra CHE_INFRA_KUBERNETES_SINGLEHOST_WORKSPACE_EXPOSURE property is needed, because we've changed the parameter name in che-server and it is not yet synced in che-operator image (will be managed with singleHostExposureType: 'gateway')
• devfile/plugin registries and keycloak are still deployed with their own Ingress/Route. (under development)

[artaleks9]

• Considering to the last created issues this issue can be closed:
  Automate testing of Single-Host CHE on OpenShift CI #18630
  Upgrade 'happy-path' test workspace to run on Che 'single-host'  #18765