Update rollbacks.md

Added the warning about 2.6.4+ rollbacks from the restore docs so that people doing rollbacks can see them without having to know to look at the restore docs
2026-09-25 12:38:05 +00:00 · 2022-12-12 09:07:43 -06:00
parent a52be2e254
commit 4c937fe6e8
1 changed files with 20 additions and 0 deletions
@@ -1,6 +1,26 @@
 ---
 title: Rollbacks
 ---
+## Additional Steps for Rollbacks with Rancher v2.6.4+
+
+In Rancher v2.6.4, the cluster-api module has been upgraded from v0.4.4 to v1.0.2 in which the apiVersion of CAPI CRDs are upgraded from `cluster.x-k8s.io/v1alpha4` to `cluster.x-k8s.io/v1beta1`. This has the effect of causing rollbacks from Rancher v2.6.4 to any previous version of Rancher v2.6.x to fail because the previous version the CRDs needed to roll back are no longer available in v1beta1.
+
+To avoid this, the Rancher resource cleanup scripts should be run **before** the restore or rollback is attempted. Specifically, two scripts have been created to assist you: one to clean up the cluster (`cleanup.sh`), and one to check for any Rancher-related resources in the cluster (`verify.sh`). Details on the cleanup script can be found in the [rancher/rancher-cleanup repo](https://github.com/rancher/rancher-cleanup).
+
+:::caution
+
+Rancher will be down as the `cleanup` script runs as it deletes the resources created by rancher.
+
+:::
+
+The additional preparations:
+
+1. Follow these [instructions](https://github.com/rancher/rancher-cleanup/blob/main/README.md) to run the scripts.
+1. Follow these [instructions](https://rancher.com/docs/rancher/v2.6/en/backups/migrating-rancher/) to install the rancher-backup Helm chart on the existing cluster and restore the previous state.
+    1. Omit Step 3.
+    1. When Step 4 is reached, install the required Rancher v2.6.x version on the local cluster you intend to roll back to.
+
+:::

 ## Rolling Back to Rancher v2.5.0+