chore: fix CNI info (coder#1003)

Katie Horne · web-flow · commit ffc7f2ac375e · 2022-05-27T13:54:37.000-05:00
diff --git a/setup/kubernetes/aws.md b/setup/kubernetes/aws.md
@@ -200,7 +200,7 @@ as a workspace deployment option, you'll need to
    eksctl create nodegroup --config-file=coder-node.yaml
    ```
 
-## Step 3: Install Calico onto your cluster
+## Step 3: (Optional) Install Calico onto your cluster
 
 AWS uses
 [Calico](https://docs.amazonaws.cn/en_us/eks/latest/userguide/calico.html) to
diff --git a/setup/kubernetes/azure.md b/setup/kubernetes/azure.md
@@ -96,18 +96,9 @@ az aks create \
   --min-count 2 \
   --node-vm-size Standard_B8ms \
   --network-plugin "kubenet" \
-  --network-policy "calico"
+  --network-policy "azure"
 ```
 
-> [AKS offers built-in support](https://docs.microsoft.com/en-us/azure/aks/use-network-policies#create-an-aks-cluster-and-enable-network-policy)
-> for the
-> [Calico](https://docs.projectcalico.org/getting-started/kubernetes/managed-public-cloud/gke)
-> network policy engine, and you can opt-in by including the
-> `--network-policy "calico"` flag.
->
-> However, you can only choose Calico as your network policy option when you
-> create the cluster; you cannot enable Calico on an existing cluster.
-
 This process might take some time (~5-20 minutes), but if you're successful,
 Azure returns a JSON object with your cluster information.
 
