This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 68%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
Hello,
Is anyone using Azure cni overlay in production environment. If yes, can someone provide the feedback. Are there any issues regarding performance or connectivity or any bad experiences etc.
Just wanted to know if overlay approach is healthy and has no bugs so that we can go ahead to create new AKS.
Thank you.
DISCLAIMER:- Strictly asked the personal experiences of the users as it is general available since April only.
@AirGordon Any suggestions on this please?
I have ample amount of Ip's available. Its just that I am creating a new AKS infra for which I thought to use it
.......
Hi @Tanul
Thanks for reaching Microsoft Q&A.
I´ve checked internally and for now we only have a scenario that might be consider as a bug for the AKS operation to migrate a cluster from legacy Azure CNI to Overlay (https://learn.microsoft.com/en-us/azure/aks/azure-cni-overlay#upgrade-an-existing-cluster-to-cni-overlay).
Cluster had both the old azure-ip-masq-agent-config configmap as well as the azure-ip-masq-agent-config-reconciled configmap with the nonMasqueradeCIDRs populated with VNET, nodes subnet and service CIDR.
Once run the update to Overlay, only the azure-ip-masq-agent-config-reconciled got updated to remove all nonMasqueradeCIDR, and only include the pod CIDR there.
This can break some of the pods traffic because the pods were not getting the traffic SNAT when it was sent to some address spaces in Azure network setup.
If you have any type of bug/connectivity/latency, please report to us by opening a support ticket on the Azure Portal so we can check/drive internally. Also, I advise you to follow our github page where you can find weekly updates/bug/new releases for AKS.
Hope this helps. Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.
@Eddie Neto My query is regarding new AKS. I am not doing any migration.. Its a completely new build from scratch. In that case, is there any performance issue coming. Because, for 4 years we are using Azure CNI in our old AKS and we have never faced any network related issue. But, now we are deleting those AKS and recreating new one's..
As this overlay is a new thing for me and recently got into GA. I wanted to know is there any network related issues coming or any other bug. Is the performance of this overlay is exactly same as the simple Azure CNI or still there is a marginal difference where simple azure cni is better in speed and connectivity.
@Eddie Neto I'm asking this question as part of my impact analysis as I don't have much of IP shortage problem here. I can go with Azure CNI without overlay as well. But no one can predict the future and that is why if azure cni overlay is 100% same in performance, speed and connectivity in comparison to the simple azure cni then I can go with overlay networking as well.
Thanks for your quick reply. For now, creating brand new AKS cluster, there is no know issue so far. The only issue that exists so far is related to migration, which does not apply on your case.
Hope this helps. Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.