Skip to content

Commit e6fa779

Browse files
committed
updates region availability
1 parent 93569b8 commit e6fa779

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

articles/aks/configure-azure-cni-static-block-allocation.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.author: allensu
77
ms.service: azure-kubernetes-service
88
ms.subservice: aks-networking
99
ms.topic: article
10-
ms.date: 02/29/2024
10+
ms.date: 03/14/2024
1111
ms.custom: references_regions, devx-track-azurecli
1212
---
1313

@@ -52,6 +52,15 @@ Below are some of the limitations of using Azure CNI Static Block allocation:
5252
`max_pods` = (N * 16) - 1`
5353
where N is any positive integer and N > 0
5454
55+
### Region availability
56+
57+
This feature is **_not_** available in the following regions:
58+
59+
- US South
60+
- EastUS2
61+
- WestUS
62+
- WestUS2
63+
5564
## Plan IP addressing
5665
5766
Planning your IP addressing is much simpler with this feature. Since the nodes and pods scale independently, their address spaces can also be planned separately. Since pod subnets can be configured to the granularity of a node pool, you can always add a new subnet when you add a node pool. The system pods in a cluster/node pool also receive IPs from the pod subnet, so this behavior needs to be accounted for.

0 commit comments

Comments
 (0)