Helm - registries does not work with default-host

[sparkoo]

Describe the bug

When deploying che with helm in default-host mode, devfile and plugin registries are deployed, but does not work.

depoy command:
helm upgrade --install che --force --namespace che --set global.ingressDomain=$(minikube ip) --set global.serverStrategy=default-host --set cheImage=eclipse/che-server:nightly deploy/kubernetes/helm/che/

Registries chart templates ignore defaul-host settings and create these invalid hosts:

==> v1beta1/Ingress
NAME              HOSTS                               ADDRESS         PORTS  AGE
che-ingress       *                                   192.168.122.66  80     83m
devfile-registry  devfile-registry-che.192.168.39.34  80              1s
plugin-registry   plugin-registry-che.192.168.39.34   80              1s

Che version

• latest

Steps to reproduce

1. at local filesystem go to dir where you have che sources
2. run the deploy helm command from the description
3. go to minikube ip in your browser
4. try to create workspace. It won't work, because devfile registry has wrong url. You can check by checking browser communication via browser devtools.

Expected behavior

The registries should work by default with helm charts and default-host. The registries should be deployed under url path something like /devfile-registry and /plugin-registry, but we have to be sure it won't conflict with anything else.

Runtime

• minikube (include output of minikube version and kubectl version)

Screenshots

Installation method

• helm (see description)

Environment

• my computer
  • Linux

Workaround

deploy registries manually and set --set cheDevfileRegistry.deploy=false --set che.workspace.devfileRegistryUrl=${DEVFILE_REGISTRY_URL} --set chePluginRegistry.deploy=false --set che.workspace.pluginRegistryUrl=${PLUGIN_REGISTRY_URL} in the helm deploy

Additional context

#13647

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.