Skip to content

Commit 540835d

Browse files
Update articles/aks/nat-gateway.md
Co-authored-by: Chase Wilson <[email protected]>
1 parent 9f4c299 commit 540835d

1 file changed

Lines changed: 0 additions & 3 deletions

File tree

articles/aks/nat-gateway.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,6 @@ This article shows you how to create an Azure Kubernetes Service (AKS) cluster w
2828
* If no zone is specified when creating a managed NAT gateway, then NAT gateway is deployed to "no zone" by default. When NAT gateway is placed in **no zone**, Azure places the resource in a zone for you. For more information on non-zonal deployment model, see [non-zonal NAT gateway](/azure/nat-gateway/nat-availability-zones#non-zonal).
2929
* A managed NAT gateway resource can't be used across multiple availability zones.
3030

31-
> [!IMPORTANT]
32-
> If no value for the outbound IP address is specified, the default value is one.
33-
3431
```azurecli-interactive
3532
az aks create \
3633
--resource-group myResourceGroup \

0 commit comments

Comments
 (0)