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(73.60000000000001, 17%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
After SP renewal, node scaled up in agent pools even when the condition for scaling was manual
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
![](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(268.8, 61%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGV%3C/text%3E%3C/svg%3E)
Hi Sajin Seby,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
We understand from your query that you are experiencing an issue with node count increases when you renewed SP.
It appears that the growth in node numbers may be because of automated functionality within AKS, such as the Cluster Auto scaler, which may have been activated following the SP renewal. When the Service Principal was renewed, it may have reinstated permissions or activated a policy to enable autoscaling to take place, particularly if there were resource requirements.
It's also conceivable that certain automated tasks or scripts involving the SP renewal inadvertently caused scaling activities. To avoid this in the future, I'd recommend verifying the autoscaling configuration and checking any automation associated with the SP to make sure everything is set up as desired.
If the comment was helpful, please don't forget to upvote.
Thank you.
Hi Geethasri,
Thanks for the update. I have verified that the autoscaling is false by default and the scale method within the node pools is in the manual state even after the SP renewal. Also verified that no automation is configured wrt SP renewal. This is the 2nd time I've faced the issue this month!
Thank You.
Hi Sajin Seby,
It seems like something out of the ordinary initiated the scaling, despite autoscaling and manual scaling being properly configured. It might be that the SP renewal somehow triggered a reset or conflict in AKS configurations, resulting in unexpected behavior.
It might also be caused by an unseen dependency or default behavior in Azure following the SP renewal, even if no automation is implemented on your side. Since this happened twice this month, I’d recommend closely monitoring the AKS activity logs around the renewal time to see if any other changes or system-level actions are occurring that could be influencing scaling.
If everything checks out, a support ticket with Azure might help uncover any underlying platform issues.
If you have any further queries, please let us know we are glad to help you.
Hi Geethasri,
I could not find the option to raise a ticket. Every time I try to create a support ticket, it takes me to either documentation or Q&A page.
Hi Sajin Seby,
Please go through this document for your reference
https://learn.microsoft.com/en-us/azure/aks/scale-cluster?source=recommendations&tabs=azure-cli
If you have any further question let me know.
Thank you.