Plugin brokering fails TLS, self-signed certificates and embedded registries

[davidfestal]

Describe the bug

When running Che with TLS, self-signed certificates enabled, and embedded registries (deployed behind Openshift routes), the plugin broker fails when trying to access the plugin registry because the certificate is unknown.

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

With the Operator or Che Ctl, install Che with the following custom resource:

apiVersion: org.eclipse.che/v1
kind: CheCluster
metadata:
  name: eclipse-che
spec:
  server:
    cheImageTag: nightly
    devfileRegistryImage: 'quay.io/eclipse/che-devfile-registry:nightly'
    pluginRegistryImage: 'quay.io/eclipse/che-plugin-registry:nightly'
    tlsSupport: true
    selfSignedCert: true
  auth:
    openShiftoAuth: true
    identityProviderImage: 'eclipse/che-keycloak:nightly'
  storage:
    pvcStrategy: per-workspace
    pvcClaimSize: 1Gi
    preCreateSubPaths: true

And try to start a workspace. You will have an error coming from the plugin broker.

Expected behavior

Workspace should start correctly.

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)

Screenshots

Installation method

• chectl
• che-operator
• minishift-addon
• I don't know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: please specify

Additional context

[slemeur]

LGTM

[sleshchenko]

Should be fixed by eclipse-che/che-plugin-broker#67 and #14089