RKE1 cluster provisioning shift to Cluster API v2prov in Rancher 2.6+

Operators need to decide how to handle existing RKE1‑provisioned clusters as Rancher shifts its default provisioning path to the Cluster API‑based v2prov framework for RKE2 and K3s clusters. Since Rancher does not provide an in‑place upgrade from RKE1 to RKE2/K3s, the choice is between maintaining the legacy RKE1 path until it is officially deprecated or rebuilding each workload cluster on the newer provisioning stack. The decision must consider the current Rancher version’s support matrix, the lack of a migration tool that preserves the control plane, and the operational impact of cluster replacement on workload availability and backup strategies.

What is the announced deprecation timeline for RKE1 support in Rancher 2.6+ releases? How should teams evaluate the trade‑offs between continuing to run RKE1 clusters and investing in a full cluster rebuild on RKE2/K3s, including any available workload migration aids? Are there any Rancher‑endorsed procedures or third‑party tools that allow a safe transition of workloads without requiring a new cluster provisioning step?