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(316.8, 92%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAP%3C/text%3E%3C/svg%3E)
In our company account, we are in the process of updating the version of kubernetes from 1.24.1 (current) to 1.27.x. We are currently using a node pool running ubuntu version 18.04, this version from Azure documentation does not support kubernetes version 1.27.x. The problem is that currently via the azure portal itself we can neither upgrade nor create a new node pool with ubuntu version 22.04. Can you tell us which is the correct way to proceed with the upgrade, without incurring in downtime?
![](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(105.60000000000001, 79%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
Welcome to the Microsoft Q&A Platform. Thank you for posting your query here. We are looking into it and will get back to you soon.
Thank you.
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
First, upgrade Kubernetes to version 1.27.x while continuing to use the existing node pool with Ubuntu 18.04. This will update the control plane to the new version, allowing you to confirm that everything is functioning correctly.
Create a new node pool with Ubuntu 22.04. This will allow you to create a new node pool without affecting the existing one. Once the new node pool is created, migrate all workloads. Drain and cordon the old node pool running Ubuntu 18.04 to prevent new pods from being scheduled on it.
Once the upgrade is complete, you can delete the old node pool running Ubuntu 18.04.
Therefore, it is a safe way to create a new cluster first and then deploy existing workloads to the new cluster and see if they are working properly.
If you have any further queries, do let us know.
If the answer is helpful, please click "Accept Answer" and "Upvote it."
Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.