![](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(118.4, 21%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELP%3C/text%3E%3C/svg%3E)
Windows for business | Windows Server | Storage high availability | Clustering and high availability
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi Lucas ！
Thank you for contacting the Microsoft Community!
Regarding your cluster upgrade issue, we also refer to the previous link.：https://learn.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade
（1）You need to go from 2016 to 2019, and then from 2019 to 2022. This can ensure that there are no changes to your cluster role.
PS：Don't forget to run the command: Update-ClusterFunctionalLevel
（2）However, if you haven't deployed the SQL AG role yet, I think it's feasible for you to directly upgrade the node systems of the cluster to 2019, and then create a new cluster (of course, you can use the previous cluster name CNO and cluster IP), and deploy the AG role within the new cluster.
In conclusion, both methods are feasible. The steps in Plan Two might be challenging, while Plan One is safer. I wish you all the best!
Best Regards，
Andrew