-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
0
-
0%
-
-
-
Azure Red Hat Openshift
1. Proposed title of this feature request
MUO should be able to access api.openshift.com via PrivateLink/Egress Lockdown
2. What is the nature and description of the request?
CX report
We are trying to update cluster but getting error as below. I believe its connectivity problem reaching to api.openshift.com
but cluster is enabled with egress lockdown so api.openshift.com should be accessible on private link but looks like connectiong is going via proxy.
After some internal searching, I found the MUO requires direct access to api.openshift.com to retrieve the upgrade graph.
It seems somehow it can not go through the private link/egress lockdown
A potential workaround might involve adding a route to api.openshift.com in Azure Firewall settings, enabling MUO to access the required endpoint.
3. Why does the customer need this? (List the business requirements here)
CX like all the traffic go through egress locked as the document described
4. List any affected packages or components.
MUO