-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
-
False
-
None
-
False
-
0
-
0
-
0
In OCM, all Hypershift-related clusters are private.
Since the management cluster is private, this is causing issues when the console operator tries to expose the console publicly.
I see this message in the console co:
DeploymentAvailable: 0 replicas available for console deployment
RouteHealthAvailable: route not yet available, https://console-openshift-console.apps.sbarouti250.brut.hypershift.sdev.devshift.net
returns '503 Service Unavailable'
I looked into the logs of the console pod, and found this:
error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-ocm-sbarouti-1smk0snbj76vmvf6amnl6c4hpcsph8lt-s-8dcac55c.apps.hshifti01ue1.z3pt.p1.openshiftapps.com:443/oauth/token
failed: Head "https://oauth-ocm-sbarouti-1smk0snbj76vmvf6amnl6c4hpcsph8lt-s-8dcac55c.apps.hshifti01ue1.z3pt.p1.openshiftapps.com:443
": context deadline exceeded (Client.Timeout exceeded while awaiting headers)