Hi, my org is running RKE2 on v1.21.5+rke2r1, so I have couple of questions please: 1. from v1.21.5 can we do v1.21.14 rite? 2. from v1.21.14 can we directly upgrade to v1.22.17+rke2r1 3. the upgrade will be done on both control plane and worder nodes?

v1.21 is perhaps EOL - oldest version I see is 1.23 on support matrix: https://www.suse.com/suse-rke2/support-matrix/all-supported-versions/rke2-v1-23/

yes, best practice is to go to latest on your current minor, then to latest on the next minor. continue until you’re on a supported minor.

thank you. Cluster was build using Scripts, so how different will it be?

https://github.com/rancher/rke2/blob/release-1.21/docs/upgrade/basic_upgrade.md#upgrade-rke2-using-the-installation-script You want to do the 3rd curl command for specific version... this one:

curl -sfL <https://get.rke2.io> | INSTALL_RKE2_VERSION=vX.Y.Z-rc1 sh -

the system-upgrade-controller should work fine even that far back

great thank you, one final question, these upgrades have to be done on both control plane and worker nodes correct?

if you’re doing it by hand, yes

thank you @creamy-pencil-82913 and @hundreds-evening-84071

did you deploy the system upgrade controller and CRDs?

Since we have our network air gapped I could not deploy so I guess that is why the error has triggered. So what I understand is system controller is build around the controller, so it will spawn pods to do the upgrade and it will upgrade all the master nodes along with its worker nodes? Couple of questions I have are: 1. we have Rancher with the management server, then we have the control plane, since both have controller do we run the system-contoller on both of them or just run on rancher management? 2. as mentioned above our network is air-gapped will there anything different or we should just have to add upgrade.cattle.io/v1 to the repository?