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(307.2, 36%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EUF%3C/text%3E%3C/svg%3E)
I am upgrading my AKS cluster from version 1.27.x to 1.29.x. The upgrade process involves updating the control plane first, then creating new node pools with the same configuration as the old ones but with the newer version. After that, I drain and delete the old node pools.
After following this procedure for all node pools, I've noticed that the network out bytes are significantly higher in the new node pools compared to the old ones, and this increase persists even a week after the upgrade. I need to understand why this is happening.
Hello Umar Farook
Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.
This issue needs deeper investigation. Support team will be able to check and help on this. I would recommend you to open a azure support case.