Skip to content

Commit 2bf2156

Browse files
authored
Remove note about Calico network policies in kubenet docs
AKS kubenet docs had a note about enabling Calico network policies. We're trying to encourage people to move to Azure CNI Overlay, and enabling Calico introduces a separate step in this migration (first remove Calico, then upgrade to Overlay). Since we already have docs about enabling Calico elsewhere, remove the note about enabling Calico from the kubenet docs.
1 parent 1c89ca3 commit 2bf2156

File tree

1 file changed

+0
-13
lines changed

1 file changed

+0
-13
lines changed

articles/aks/configure-kubenet.md

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -153,19 +153,6 @@ For more information to help you decide which network model to use, see [Compare
153153
* The pod IP address range is used to assign a */24* address space to each node in the cluster. In the following example, the *--pod-cidr* of *10.244.0.0/16* assigns the first node *10.244.0.0/24*, the second node *10.244.1.0/24*, and the third node *10.244.2.0/24*.
154154
* As the cluster scales or upgrades, the Azure platform continues to assign a pod IP address range to each new node.
155155
156-
> [!NOTE]
157-
> If you want to enable an AKS cluster to include a [Calico network policy][calico-network-policies], you can use the following command:
158-
>
159-
> ```azurecli-interactive
160-
> az aks create \
161-
> --resource-group myResourceGroup \
162-
> --name myAKSCluster \
163-
> --node-count 3 \
164-
> --network-plugin kubenet \
165-
> --network-policy calico \
166-
> --vnet-subnet-id $SUBNET_ID
167-
> ```
168-
169156
### Create an AKS cluster with user-assigned managed identity
170157
171158
#### Create a managed identity

0 commit comments

Comments
 (0)