Hello Yusheng Qian
The Microsoft Document clearly state that the custom domain is a prerequisite when using Azure Front Door to expose applications from a private ARO cluster
Which means you cannot use Azure Front Door to access a private Azure Red Hat OpenShift (ARO) application without a custom domain.
It does mention that a custom domain is typically required for the setup to work correctly, especially since it states that all DNS servers are hosted on Azure, and the applications need to be exposed with a predefined hostname.
This is because:
- Azure Front Door requires TLS termination, which needs a certificate tied to a domain.
- ARO routes traffic based on host headers, which must match the domain.
- DNS mapping is essential for Private Link to function correctly.
Here's what you can try or consider
- Register a custom domain (e.g., via Azure DNS or any registrar).
- Create a DNS zone and map it to your Front Door endpoint.
- Configure TLS using Azure-managed or custom certificates.
- Set up Private Link to securely connect Front Door to your private ARO ingress.
- Using Azure Private Link in your configuration, ensure that it’s properly set up and the Azure Front Door can reach your OpenShift application. This includes verifying that the Private Link service can respond to requests as expected.
- Enable logging for Azure Front Door and look for any further details on the "Service Unavailable" error. It might help to pinpoint the problem in the routing or connectivity between Front Door and your application.
I hope these helps. Let me know if you have any further questions or need additional assistance.
Also, if these answers your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.