--pod-cidr option in CLI for Kubenet Cluster Upgrade to azure CNI

[manasij12]

Document mentions that :

Since the cluster is already using a private CIDR for pods which doesn't overlap with the VNet IP space, you don't need to specify the --pod-cidr parameter and the Pod CIDR will remain the same.

This is misleading that the command does not throw error when --pod-cidr is used. And it does not explicity mention that the --pod-Cidr should not be used to update the pod-cidr, instead it feels "the pod-Cidr will remain same if the parameter is not used"

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 64f0ba71-573f-b860-1c2c-802a62cae120
• Version Independent ID: 28990db8-fce7-c356-da6f-c052a9c201ee
• Content: Configure Azure CNI Overlay networking in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
• Content Source: articles/aks/azure-cni-overlay.md
• Service: azure-kubernetes-service
• Sub-service: aks-networking
• GitHub Login: @asudbring
• Microsoft Alias: allensu

[SaibabaBalapur-MSFT]

@manasij12 Thanks for your feedback! We will investigate and update as appropriate.

[PesalaPavan]

@manasij12 Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!