Hi @Ankur Jain ,
Update - 8/25
Question: Is it possible to remove all old cni nodepool and create new nodepool with new cni? Not asking about the co-existence of both nodepool types in the existing cluster.
Answer: In the future release plan (shared below), this is how it will work -
Customers will be able to create new node pool with new CNI in their old clusters, move workloads from node pool running old CNI to the one running new CNI and then delete the old node pool.
Update - 8/24
Question: Could you please help if it is possible to migrate all old cni nodepool including small nodepool to enhanced cni and that way we can move old cluster to new dynamic cni ?
Based on the additional details you provided on your question, I reached out to the Product team to get more information and clarity on your ask.
They confirmed that - Unfortunately, this is not possible today. But they are working to build a solution that will allow customers to create new node pools in their old clusters with the new CNI and support co-existence of the two versions of the CNI in the same cluster. This should help scenarios like yours. They are discussing to build this capability in the upcoming semester. So this is something definitely on their roadmap but not supported at this point.
Hope that helps. Let me know if you have any other specific questions that I can help you with.
8/23
Query: Is it possible to change the existing AKS cluster from normal Azure CNI to dynamic allocation of IPs and enhanced subnet support?
You can’t add dynamic allocation of IPs and enhanced subnet support on an existing AKS cluster, since all cluster/node pools need to be either normal CNI or enhanced CNI. You would need to create a new cluster with the dynamic allocation of IPs and enhanced subnet support and migrate your workloads.
You can find more details on Dynamic allocation of IP addresses and enhanced subnet support in the FAQs here.
Hope that clarifies. Let me know if you have any questions or concerns.