Skip to content

Commit 2b2714d

Browse files
more fixes
1 parent 0301ca9 commit 2b2714d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/spring-apps/how-to-create-udr-instance.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.custom: devx-track-java, devx-track-azurecli
1515

1616
**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
1717

18-
This article describes how to secure outbound traffic from your Azure Spring Apps applications. It provides a simple example of a user-defined route (UDR) instance. UDR is an advanced feature that lets you fully control egress traffic. It may be used in scenarios such as disallowing an Azure Spring Apps auto-generated public IP.
18+
This article describes how to secure outbound traffic from your Azure Spring Apps applications. It provides an example of a user-defined route (UDR) instance. UDR is an advanced feature that lets you fully control egress traffic. It may be used in scenarios such as disallowing an Azure Spring Apps auto-generated public IP.
1919

2020
## Prerequisites
2121

@@ -27,7 +27,7 @@ This article describes how to secure outbound traffic from your Azure Spring App
2727
- [Customer responsibilities for running Azure Spring Apps in VNET](vnet-customer-responsibilities.md)
2828
- [Customize Azure Spring Cloud egress with a User-Defined Route](concept-outbound-type.md)
2929

30-
## Azure Spring Apps UDR instance example
30+
## Create a VNet instance using a user-defined route
3131

3232
The following illustration shows an example of an Azure Spring Apps VNet instance using a user-defined route.
3333

@@ -141,7 +141,7 @@ FWPUBLIC_IP=$(az network public-ip show -g $RG -n $FWPUBLICIP_NAME --query "ipAd
141141
FWPRIVATE_IP=$(az network firewall show -g $RG -n $FWNAME --query "ipConfigurations[0].privateIpAddress" -o tsv | tr -d '[:space:]')
142142
```
143143

144-
### Create a UDR with a hop to Azure Firewall
144+
### Create a user-defined route with a hop to Azure Firewall
145145

146146
Azure automatically routes traffic between Azure subnets, virtual networks, and on-premises networks. If you want to change Azure's default routing, create a route table.
147147

@@ -172,7 +172,7 @@ az network firewall network-rule create -g $RG -f $FWNAME --collection-name 'asa
172172
az network firewall application-rule create -g $RG -f $FWNAME --collection-name 'aksfwar' -n 'fqdn' --source-addresses '*' --protocols 'http=80' 'https=443' --fqdn-tags "AzureKubernetesService" --action allow --priority 100
173173
```
174174

175-
### Associate the route tables to Subnets
175+
### Associate route tables with subnets
176176

177177
To associate the cluster with the firewall, the dedicated subnet for the cluster's subnet must reference the route table you created. App and service runtime subnets must be associated with corresponding route tables. The following example shows how to associate a route table with a subnet.
178178

0 commit comments

Comments
 (0)