From 995ea50b75e3f34e5302aaf95b03d1dc6ab9a131 Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Thu, 24 Mar 2022 11:07:10 -0400 Subject: [PATCH 1/3] Added statement on using scripts to clean up cluster --- .../rancher/v2.6/en/backups/restoring-rancher/_index.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/rancher/v2.6/en/backups/restoring-rancher/_index.md b/content/rancher/v2.6/en/backups/restoring-rancher/_index.md index 1f20f311720..b818387ff47 100644 --- a/content/rancher/v2.6/en/backups/restoring-rancher/_index.md +++ b/content/rancher/v2.6/en/backups/restoring-rancher/_index.md @@ -5,6 +5,13 @@ weight: 2 A restore is performed by creating a Restore custom resource. +--- +**New Requirement for Restore in HA Rancher:** + +The HA Rancher server is not coming up active when restoring Rancher with a backup taken in v2.6.3. To work around this issue, you must manually clean up the cluster **before** restoring the backup. Two scripts have been created to assist you: one to clean up the cluster, and one to check for any Rancher-related resources in the cluster. Refer [here](https://github.com/rancherlabs/support-tools/tree/master/cleanup-rancher-k8s-resources) for details on the scripts. + +--- + > **Important** > > * Follow the instructions from this page for restoring rancher on the same cluster where it was backed up from. In order to migrate rancher to a new cluster, follow the steps to [migrate rancher.]({{}}/rancher/v2.6/en/backups/migrating-rancher) From e7a8b79540b6ce614b0078e113bfedd1b22ddfaf Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Thu, 24 Mar 2022 18:46:05 -0400 Subject: [PATCH 2/3] Updating per feedback --- content/rancher/v2.6/en/backups/restoring-rancher/_index.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.6/en/backups/restoring-rancher/_index.md b/content/rancher/v2.6/en/backups/restoring-rancher/_index.md index b818387ff47..0298e5cee38 100644 --- a/content/rancher/v2.6/en/backups/restoring-rancher/_index.md +++ b/content/rancher/v2.6/en/backups/restoring-rancher/_index.md @@ -6,9 +6,11 @@ weight: 2 A restore is performed by creating a Restore custom resource. --- -**New Requirement for Restore in HA Rancher:** +**Caution:** Before performing a restore or rollback, note the following: -The HA Rancher server is not coming up active when restoring Rancher with a backup taken in v2.6.3. To work around this issue, you must manually clean up the cluster **before** restoring the backup. Two scripts have been created to assist you: one to clean up the cluster, and one to check for any Rancher-related resources in the cluster. Refer [here](https://github.com/rancherlabs/support-tools/tree/master/cleanup-rancher-k8s-resources) for details on the scripts. +- 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 [rancherlabs/support-tools repo](https://github.com/rancherlabs/support-tools/tree/master/cleanup-rancher-k8s-resources). --- From 014892459336d6a0f708a42eedf91aa6ad33892e Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Thu, 24 Mar 2022 18:48:25 -0400 Subject: [PATCH 3/3] Fixed typo --- content/rancher/v2.6/en/backups/restoring-rancher/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/backups/restoring-rancher/_index.md b/content/rancher/v2.6/en/backups/restoring-rancher/_index.md index 0298e5cee38..468b179d348 100644 --- a/content/rancher/v2.6/en/backups/restoring-rancher/_index.md +++ b/content/rancher/v2.6/en/backups/restoring-rancher/_index.md @@ -8,7 +8,7 @@ A restore is performed by creating a Restore custom resource. --- **Caution:** Before performing a restore or rollback, note the following: -- 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. +- 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 [rancherlabs/support-tools repo](https://github.com/rancherlabs/support-tools/tree/master/cleanup-rancher-k8s-resources).