Skip to content

AKS Learn feedback: Whether a manual upgrade is possible #210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
torumakabe opened this issue Apr 23, 2025 · 0 comments
Open

AKS Learn feedback: Whether a manual upgrade is possible #210

torumakabe opened this issue Apr 23, 2025 · 0 comments
Labels

Comments

@torumakabe
Copy link

Type of issue

Missing information

Feedback

As this article explains, AKS Automatic cluster upgrades are pre-configured; however, is it possible to perform an upgrade manually? Automatic upgrades are fine in principle, but there are times when I’d like to trigger one manually when I’m prepared to take the risk.

I tried to start the upgrade in the portal but couldn’t; however, I was able to do it by changing the kubernetesVersion in the Bicep code and redeploying. Is this a supported approach?

Note that when I changed the kubernetesVersion, the NAP node pool was upgraded, but the VMSS system node pool was not. I was able to upgrade it by separately changing the system node pool’s orchestratorVersion and redeploying. Is this intended behavior?

Page URL

https://learn.microsoft.com/en-us/azure/aks/intro-aks-automatic

Content source URL

https://github.com/MicrosoftDocs/azure-aks-docs/blob/main/articles/aks/intro-aks-automatic.md

Author

@sabbour

Document Id

996a5f43-bb9b-a3b8-9e51-ca31c5272d1a

Platform Id

14d2d9ba-2814-325c-27fd-2cea27b7e5aa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant