After migration of Rancher between different Kubernetes distriubtions, via the rancher-backup operator, the local cluster distribution within Rancher is not updated

Article Number: 000021577

Environment

Rancher 2.5+

Situation

Migration of Rancher from one Kubernetes distribution to another, e.g. from K3s to RKE2, using the Rancher Backup Operator.

Cause

The rancher-backup operator performs a restore of Rancher configuration resources, without manipulating any of these in the process. As a result, when migrating Rancher between different cluster types, values within the local cluster.management.cattle.io resource need to be manually updated to to reflect the change in distribution. Further details can be found in the GitHub issue at https://github.com/rancher/rancher/issues/42158

Resolution

Follow the documented steps at the end of point 2. Restore from backup using a Restore custom resource in the Rancher migration documentation, to update the distribution version of the Rancher local cluster within the Rancher state.