Once deployed, your environment will show Windows Server 20 nodes, with the workloads running on the 2019 nodes: kubectl get nodes -o wide If you have an application deployed already, follow the recommended steps to deploy a new node pool with Windows Server 2022 nodes. Apply the new YAML file to the existing workload You should leverage the same YAML file you used to deploy the application in the first place - this ensures no other configuration is changed, only the nodeSelector and the image to be used.

You can get this information from the previous step on which you created a new version of the containerized application by changing the FROM statement on your dockerfile. Once you update the nodeSelector on the YAML file, you should also update the container image to be used. To accomplish this, one option is to use a different annotation: nodeSelector: When upgrading from Windows Server 2019 to Windows Server 2022, you need to enforce not only the placement on a Windows node, but also on a node that is running the latest OS version.

The above annotation finds any Windows node available and places the pod on that node (following all other scheduling rules). To use Node Selector, make the following annotation to your YAML files: nodeSelector: Node Selector is the most common and recommended option for placement of Windows pods on Windows nodes. To upgrade your application, you need a separate node pool for Windows Server 2022.įor more information on how to add a new Windows Server 2022 node pool to an existing AKS cluster, see Add a Windows Server 2022 node pool. Windows Server 20 can't co-exist on the same node pool on AKS. Add a Windows Server 2022 node pool to the existing cluster Check out Dockerfile on Windows and Optimize Windows Dockerfiles to learn more about how to build a dockerfile for Windows workloads.

Windows node update