In four steps that you carry out yourself: first, create a new cluster, second, transfer the images to the Private Registry, third, point manifests or the GitOps source to the new cluster, fourth, transfer the volume data and change the DNS record. Both clusters run side by side until the new one carries the traffic. Versions 1.37, 1.36 and 1.35 can be selected for the new cluster; the GitOps source is the Git repository from which Argo CD or Flux sync.
The names of the StorageClasses (the storage profiles for volumes), the annotations of the previous Load Balancer and your Ingress objects need to be adjusted: these will continue to run as soon as they carry the Ingress class cilium; Cilium, the network plugin of the cluster, does not evaluate annotations from ingress-nginx.
During the transition period, Managed Rancher can manage the old cluster alongside the new one. The range that Rancher 2.15 manages applies to both: Kubernetes 1.34 to 1.36.