[Enter feedback here]

Doc URL: https://learn.microsoft.com/en-us/azure/openshift/howto-restrict-egress#red-hat-telemetry-and-red-hat-insights

From "Red Hat Telemetry and Red Hat Insights" section in above doc, it says "console.redhat.com/api/ingress" should be allowed. In some case where using "URL filtering" from Azure firewall to whitelist the "console.redhat.com/api/ingress", the TLS-inspection must be enabled, and TLS-inspection feature from Azure firewall would prevent the outbound traffic from connecting to "console.redhat.com/api/ingress".

This issue was solved by whitelisting the "console.redhat.com" from Azure firewall without URL filtering feature.

So we may need to do some modification or add a comment to clarify that in some case where using "URL filtering" from Azure firewall, we need to allow the "console.redhat.com" instead of whitelist the URL "console.redhat.com/api/ingress".

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 1cbdc700-aa37-77ab-7f19-fc783cded33e
• Version Independent ID: b311b772-4239-be60-b66d-bc1143a56b53
• Content: Restrict egress traffic in an Azure Red Hat OpenShift (ARO) cluster - Azure Red Hat OpenShift
• Content Source: articles/openshift/howto-restrict-egress.md
• Service: azure-redhat-openshift
• GitHub Login: @joharder
• Microsoft Alias: joharder