Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update network-topology-connectivity.md to reflect app gateway should not be used with ingress controller #1372

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update network-topology-connectivity.md to reflect app gateway should not be used with ingress controller #1372

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...scenarios/app-platform/azure-red-hat-openshift/network-topology-connectivity.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Use incoming (ingress) controllers to expose applications running in the Azure R
- [Ingress controllers](https://docs.openshift.com/container-platform/latest/networking/ingress-operator.html) provide application-level routing with only a slight increase in complexity.
- Azure Red Hat OpenShift creates a generic DNS entry that simplifies access to exposed applications in the cluster. An example DNS entry is `*.apps.<cluster-ID>.<region>.aroapp.io`. It's useful for a private cluster to route traffic for the application.
- Azure Red Hat OpenShift offers a built-in [Ingress controller and routes](https://docs.openshift.com/container-platform/latest/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.html).
- You can use Azure Red Hat OpenShift ingress with [Azure Front Door](/azure/openshift/howto-secure-openshift-with-front-door).
- You can use Azure Red Hat OpenShift ingress with [Azure Front Door](/azure/openshift/howto-secure-openshift-with-front-door). **Note** that using Application Gateway with Azure Red Hat Openshift ingress controllers defined as backend settings is **NOT** supported due to service chaining. Follow the design guidance in this article.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- You can use Azure Red Hat OpenShift ingress with [Azure Front Door](/azure/openshift/howto-secure-openshift-with-front-door). **Note** that using Application Gateway with Azure Red Hat Openshift ingress controllers defined as backend settings is **NOT** supported due to service chaining. Follow the design guidance in this article.
- You can use Azure Red Hat OpenShift ingress with [Azure Front Door](/azure/openshift/howto-secure-openshift-with-front-door). Using Azure Application Gateway with Azure Red Hat OpenShift ingress controllers defined in backend pools is not supported due to service chaining. Follow the design guidance in this article.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you have a link to include here that defines service chaining so a customer understands why that is a bad thing?

- Align your configuration with the egress filtering design to avoid asymmetric routing. UDRs potentially might cause asymmetric routing.
- If your scenario requires [TLS termination](https://docs.openshift.com/container-platform/latest/networking/ingress-operator.html), consider how you'll manage TLS certificates.

Expand Down