Skip to content

Commit ced8cbd

Browse files
committed
Add subnet id info
1 parent 232d0d8 commit ced8cbd

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

articles/aks/egress-outboundtype.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Customize user-defined routes (UDR) in Azure Kubernetes Service (AKS)
33
description: Learn how to define a custom egress route in Azure Kubernetes Service (AKS)
44
services: container-service
55
ms.topic: article
6-
ms.date: 01/31/2020
6+
ms.date: 03/16/2020
77

88

99
#Customer intent: As a cluster operator, I want to define my own egress paths with user-defined routes. Since I define this up front I do not want AKS provided load balancer configurations.
@@ -316,7 +316,11 @@ az role assignment list --assignee $APPID --all -o table
316316

317317
### Deploy AKS
318318

319-
Finally, the AKS cluster can be deployed into the existing subnet we have dedicated for the cluster. The target subnet to be deployed into is defined with the environment variable, `$SUBNETID`.
319+
Finally, the AKS cluster can be deployed into the existing subnet we have dedicated for the cluster. The target subnet to be deployed into is defined with the environment variable, `$SUBNETID`. We didn't define the `$SUBNETID` variable in the previous steps. To get the value for the subnet ID, you can use the `az network vnet subnet list` command.
320+
321+
```azurecli
322+
az network vnet subnet list --resource-group $RG --vnet-name $VNET_NAME
323+
```
320324

321325
We will define the outbound type to follow the UDR which exists on the subnet, enabling AKS to skip setup and IP provisioning for the load balancer which can now be strictly internal.
322326

0 commit comments

Comments
 (0)