From 3f541f13630a9d621b70858b81e593945d91dc76 Mon Sep 17 00:00:00 2001 From: Marty Hernandez Avedon Date: Thu, 26 Jan 2023 10:23:56 -0500 Subject: [PATCH] Update docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md --- .../install-upgrade-on-a-kubernetes-cluster/rollbacks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md index 25f6cce7231..c1e9ea5110a 100644 --- a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md @@ -3,7 +3,7 @@ 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. +Rancher v2.6.4 upgrades the cluster-api module from v0.4.4 to v1.0.2. Version v1.0.2 of the cluster-api, in turn, upgrades the CAPI CRDs apiVersion from `cluster.x-k8s.io/v1alpha4` to `cluster.x-k8s.io/v1beta1`. The CAPI CRDs upgrade to v1beta1 causes rollbacks to fail when you attempt to move from Rancher v2.6.4 to any previous version of Rancher v2.6.x. This is because v1beta1 is missing the previous versions that the CRDs need to roll back. To avoid rollback failure, the following Rancher scripts should be run **before** you attempt a restore operation or rollback: