This message was deleted.
# rke2
a
This message was deleted.
h
If you use Rancher backup-operator then all your downstream clusters should also "move" to the new environment
and, there is also a #CC2UQM49Y channel for longhorn specific things
a
Hmm, not really, Rancher RKE is set to be EOL on July 31, 2025, so we are considering switching to RKE2. Therefore, we can't migrate Rancher itself using backup-operator since it was installed with RKE, not RKE2, right?
h
Ha, we have duplicate threads...
it should not matter.. but you do have to match versions; kubernetes version rancher version backup-operator version need to match on both RKE and RKE2 then try to backup from RKE restore to RKE2
I will recommend however if you have resources, spin up another environment in RKE and try and test doing these steps review the guide it has changed since I tried backup/restore a year ago
a
We installed it using these instructions: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster#kubernetes-cluster So, we first created an RKE Kubernetes cluster on 3 VM instances and then installed the Rancher Server using the Rancher Helm Chart. If I understand correctly, we would first install an RKE2 Kubernetes cluster on new VM instances, then use the Rancher Helm Chart to install the Rancher Server, using the same version as the old Rancher Server. After that, install the Rancher Backup Operator on both the local RKE Kubernetes cluster and the local RKE2 Kubernetes cluster, take a backup of the Rancher RKE and perform a restore on RKE2?
a
a
Thank you, In our case, the situation is as follows: We have a Rancher Server set up with RKE, and our current version is 2.7.10. We have multiple imported clusters on Rancher. We don't have any cluster created through Rancher itself. Our goal is to set up a new Rancher server with RKE2 and with a newer version of course. Since our clusters are imported, our plan is to remove them from the old RKE Rancher and re-import them into the new RKE2 Rancher. We don't need to migrate everything regarding the imported clusters; it is only important for us to transfer the Rancher options from Users & Authentication --> Users --> Role Templates --> Auth Provider. So, it is only important for us to transfer roles and users from the old RKE Rancher to the new RKE2 Rancher. Only after that would we remove the imported clusters from the old Rancher and then import them into the new RKE2 Rancher. In this case, would the Rancher-backup operator or the Cattle-drive tool help?