Skip to content
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

Windows Node Updates #1132

Open
sam-cogan opened this issue Jul 31, 2019 · 4 comments

Comments

@sam-cogan
Copy link

commented Jul 31, 2019

If you follow the FAQ page here - https://docs.microsoft.com/en-us/azure/aks/faq it indicates that to apply Windows updates to your Windows VM nodes you have to use the AZ AKS nodepool upgrade command, which recreates the nodes with the latest OS image.

This is fine, except that AZ AKS nodepool upgrade only does this if you specify a kubernetes version newer than the one you have deployed to that node pool. If you use the same version, nothing happens to the nodes. This now means that getting Windows updates is tied to upgrading my version of Kubernetes. It also means that if I am on the latest version of Kubernetes available in AKS, then I can't get Windows updates until a new version is released. This doesn't seem like the right way to do this.

Am I getting this wrong, or are there any plans to make this better?

@triage-new-issues triage-new-issues bot added the triage label Jul 31, 2019

@zhiweiv

This comment has been minimized.

Copy link

commented Aug 2, 2019

Per MicrosoftDocs/azure-docs#34407, it should be on the way.

@MikkelHegn

This comment has been minimized.

Copy link
Member

commented Aug 12, 2019

Correct - we are working on closing the gap to enable nodepool OS upgrades independent of Kubernetes upgrades. In the meantime, only option is to create new node pools and migrate workloads.

To clarify the upgrade flow, you first need to run a cluster Kubernetes version upgrade, then you will get the new OS versions available for nodepools. Same upgrade constraint existing for cluster upgrades. https://docs.microsoft.com/en-us/azure/aks/use-multiple-node-pools#upgrade-a-node-pool for reference.

@coreywagehoft

This comment has been minimized.

Copy link

commented Aug 20, 2019

Correct - we are working on closing the gap to enable nodepool OS upgrades independent of Kubernetes upgrades. In the meantime, only option is to create new node pools and migrate workloads.

To clarify the upgrade flow, you first need to run a cluster Kubernetes version upgrade, then you will get the new OS versions available for nodepools. Same upgrade constraint existing for cluster upgrades. https://docs.microsoft.com/en-us/azure/aks/use-multiple-node-pools#upgrade-a-node-pool for reference.

@MikkelHegn I didn't see independant nodepool OS upgrades on the AKS roadmap here on GitHub. Will that be added soon, so I can track progress?

@MikkelHegn

This comment has been minimized.

Copy link
Member

commented Aug 21, 2019

Tracking this here: #893

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.