Updating the Azure Front Door with ARO guide#960
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
kmcolli
left a comment
kmcolli
left a comment
There was a problem hiding this comment.
I can't make sense of the environment variables ... update those as they previously were, minimally with comments but preferable looking up values ... and I'll give it another run through.
| When you create a cluster on ARO you have several options in making the cluster public or private. With a public cluster you are allowing Internet traffic to the api and *.apps endpoints. With a private cluster you can make either or both the api and .apps endpoints private. | ||
| Azure Front Door Premium can expose applications running on an Azure Red Hat OpenShift (ARO) cluster while keeping the cluster ingress private. Azure Front Door receives public client traffic at the edge and reaches the ARO internal ingress load balancer through Azure Private Link. | ||
|
|
||
| This guide configures the following traffic flow: |
There was a problem hiding this comment.
Please create a proper diagram vs using the AI generated flow :)
There was a problem hiding this comment.
sounds good will do
| Set the ARO cluster, Azure resource group, application hostname, and Azure Front Door names: | ||
|
|
||
| ARORG=<resource group for the cluster> | ||
| ```bash |
There was a problem hiding this comment.
go back to how env variables were set in the previous guide - this is confusing and very error prone ... you should only have to set a small set of them like:
AROCLUSTER=
ARORG=
AFD_NAME=
DOMAIN='e.g. aro.kmobb.com' This is the domain that you will be adding to Azure DNS to manage.
ARO_APP_FQDN='e.g. minesweeper.aro.kmobb.com'
(note - we will be deploying an application called minesweeper to test front door. Select a domain you would like to use for the application. For example minesweeper.aro.kmobb.com ... where aro.kmobb.com is the domain you manage and have DNS access to.)
AFD_MINE_CUSTOM_DOMAIN_NAME='minesweeper-aro-kmobb-com'
(note - this should be your domain name without and .'s for example minesweeper-aro-kmobb-com)
PRIVATEENDPOINTSUBNET_PREFIX= subnet in the VNET you cluster is in. If you following the example above to create a custer where you virtual network is 10.0.0.0/20 then you can use '10.0.6.0/24'
PRIVATEENDPOINTSUBNET_NAME='PrivateEndpoint-subnet'
You don't have to use minesweeper of course ... the rest of the env variables should be set dynamically
There was a problem hiding this comment.
makes sense, let me replace this with section with simpler env vars with examples
2 participants
Summary
This PR revamps the Azure Front Door with ARO guide and validates the workflow against a private ARO cluster.
The updated guide:
503.