Description of problem:
The registry-console is exposed but not accessible via a route as well service.
The route is exposed as a passthrough and I could match that with oauth client URI as well.
Other application routes are working fine in the same cluster, the registry-console pod is also up and running.
As there is ELB present infront of OCP cluster hence just to eliminate traffic routing from ELB, we tried to add the route entry in "/etc/hosts" but no luck.
oc logs registry-console-1-c45vj
INFO: cockpit-ws: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
The cluster is configured with the OVS-multitenant plugin and default project has "0" netnamespace id.
$ sudo oc version
features: Basic-Auth GSSAPI Kerberos SPNEGO
I suppose "ELB" means something like a load balancer, or a proxy? Other people reported that a service providing the registry-console does work with a TLS passthrough route, just not with reencrypt (see bug 1599227 - however, I don't fully understand the details of that either).
Does it work without the ELB, with directly accessing the route?
I'm afraid this report does not contain any useful information to try and reproduce the problem. Please test without ELB or describe how to set that up. Reproducing also requires a YAML description of the involved service and route. Something like
oc get pods -o yaml registry-console-1-c45vj
and the same for the route. I. e. the precise steps to replicate this on a completely blank OCP cluster.