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 1845618a5bf..0d9305f1144 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 @@ -24,11 +24,14 @@ Follow the instructions from this page when: Alternative steps need to be performed for rollbacks in the following scenarios: - Rolling back from v2.6.4 and later to an earlier version of v2.6.x. - Rolling back from v2.7.7 and later to an earlier version of v2.7.x. +- Rolling back from v2.14.0 and later to an earlier version of v2.13.x. In Rancher v2.6.4, the cluster-api module is upgraded from v0.4.4 to v1.0.2. The cluster-api v1.0.2, in turn, upgrades the apiVersions of its Custom Resource Definitions (CRDs) from `cluster.x-k8s.io/v1alpha4` to `cluster.x-k8s.io/v1beta1`. Custom Resources (CRs) that use the older apiVersion (v1alpha4) are incompatible with v1beta1, which causes rollbacks to fail when you attempt to move from Rancher v2.6.4 to any previous version of Rancher v2.6.x. In Rancher v2.7.7, the app `rancher-provisioning-capi` is installed on the upstream (local) cluster automatically as a replacement for the embedded cluster-api controllers. Conflicts and unexpected errors will occur if the upstream cluster contains both the app, and Rancher v2.7.6 and earlier. Therefore, alternative steps are needed if you attempt to move from Rancher v2.7.7 to any previous version of Rancher v2.7.x. +In Rancher v2.14.0, the cluster-api module is upgraded from v1.10.6 to v1.12.2. The cluster-api v1.12.2, in turn, upgrades the apiVersions of its Custom Resource Definitions (CRDs) from `cluster.x-k8s.io/v1beta1` to `cluster.x-k8s.io/v1beta2`. Rancher backup files include Cluster API CRDs. When restoring backup data from Rancher v2.13.x to a local cluster after upgrading to v2.14.0, the Rancher Backup application first restores the v1beta1 CRDs. This fails because the v1beta2 version cannot be removed from the CRDs while v1beta2 custom resources are present in the cluster. + ### Step 1: Clean Up the Upstream (Local) Cluster To avoid rollback failure, follow these [instructions](https://github.com/rancher/rancher-cleanup/blob/main/README.md) to run the scripts **before** you attempt a restore operation or rollback: diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/faq/deprecated-features.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/faq/deprecated-features.md index 9586a24f03e..a5328b481f1 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/faq/deprecated-features.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/faq/deprecated-features.md @@ -16,6 +16,7 @@ Rancher 将在 GitHub 上发布的 Rancher 的[发版说明](https://github.com/ | Patch 版本 | 发布时间 | | ----------------------------------------------------------------- | ------------------ | +| [2.13.4](https://github.com/rancher/rancher/releases/tag/v2.13.4) | 2026 年 03 月 25 日 | | [2.13.3](https://github.com/rancher/rancher/releases/tag/v2.13.3) | 2026 年 02 月 25 日 | | [2.13.2](https://github.com/rancher/rancher/releases/tag/v2.13.2) | 2026 年 01 月 29 日 | | [2.13.1](https://github.com/rancher/rancher/releases/tag/v2.13.1) | 2025 年 12 月 18 日 | diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md index cac167bf73b..131ef9c5e23 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md @@ -15,6 +15,7 @@ title: 安装 Adapter | Rancher 版本 | Adapter 版本 | |-----------------|------------------| +| v2.13.4 | 108.0.0+up8.0.0 | | v2.13.3 | 108.0.0+up8.0.0 | | v2.13.2 | 108.0.0+up8.0.0 | | v2.13.1 | 108.0.0+up8.0.0 | diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/reference-guides/rancher-webhook.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/reference-guides/rancher-webhook.md index 4d811b5a23c..1d5e8104ce7 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/reference-guides/rancher-webhook.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/reference-guides/rancher-webhook.md @@ -20,6 +20,7 @@ Rancher 将 Rancher-Webhook 作为单独的 deployment 和服务部署在 local | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| +| v2.13.4 | v0.9.3 | ✓ | ✗ | | v2.13.3 | v0.9.3 | ✓ | ✓ | | v2.13.2 | v0.9.2 | ✓ | ✓ | | v2.13.1 | v0.9.1 | ✓ | ✓ | diff --git a/src/pages/versions.md b/src/pages/versions.md index 3460f05d232..482a4ce5986 100644 --- a/src/pages/versions.md +++ b/src/pages/versions.md @@ -17,12 +17,12 @@ Here you can find links to supporting documentation for the current released ver Community - v2.13.3 + v2.13.4 Documentation - Release Notes + Release Notes
N/A
✓
-
✓
+
N/A
@@ -102,6 +102,14 @@ Here you can find links to supporting documentation for previous versions of Ran Prime Community + + v2.13.3 + Documentation + Release Notes +
Support Matrix
+
✓
+
✓
+ v2.13.2 Documentation diff --git a/versioned_docs/version-2.13/faq/deprecated-features.md b/versioned_docs/version-2.13/faq/deprecated-features.md index 4e452e77376..b8273447289 100644 --- a/versioned_docs/version-2.13/faq/deprecated-features.md +++ b/versioned_docs/version-2.13/faq/deprecated-features.md @@ -12,6 +12,7 @@ Rancher will publish deprecated features as part of the [release notes](https:// | Patch Version | Release Date | |---------------|---------------| +| [2.13.4](https://github.com/rancher/rancher/releases/tag/v2.13.4) | March 25, 2026 | | [2.13.3](https://github.com/rancher/rancher/releases/tag/v2.13.3) | February 25, 2026 | | [2.13.2](https://github.com/rancher/rancher/releases/tag/v2.13.2) | January 29, 2026 | | [2.13.1](https://github.com/rancher/rancher/releases/tag/v2.13.1) | December 18, 2025 | diff --git a/versioned_docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md b/versioned_docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md index 1845618a5bf..0d9305f1144 100644 --- a/versioned_docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md +++ b/versioned_docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md @@ -24,11 +24,14 @@ Follow the instructions from this page when: Alternative steps need to be performed for rollbacks in the following scenarios: - Rolling back from v2.6.4 and later to an earlier version of v2.6.x. - Rolling back from v2.7.7 and later to an earlier version of v2.7.x. +- Rolling back from v2.14.0 and later to an earlier version of v2.13.x. In Rancher v2.6.4, the cluster-api module is upgraded from v0.4.4 to v1.0.2. The cluster-api v1.0.2, in turn, upgrades the apiVersions of its Custom Resource Definitions (CRDs) from `cluster.x-k8s.io/v1alpha4` to `cluster.x-k8s.io/v1beta1`. Custom Resources (CRs) that use the older apiVersion (v1alpha4) are incompatible with v1beta1, which causes rollbacks to fail when you attempt to move from Rancher v2.6.4 to any previous version of Rancher v2.6.x. In Rancher v2.7.7, the app `rancher-provisioning-capi` is installed on the upstream (local) cluster automatically as a replacement for the embedded cluster-api controllers. Conflicts and unexpected errors will occur if the upstream cluster contains both the app, and Rancher v2.7.6 and earlier. Therefore, alternative steps are needed if you attempt to move from Rancher v2.7.7 to any previous version of Rancher v2.7.x. +In Rancher v2.14.0, the cluster-api module is upgraded from v1.10.6 to v1.12.2. The cluster-api v1.12.2, in turn, upgrades the apiVersions of its Custom Resource Definitions (CRDs) from `cluster.x-k8s.io/v1beta1` to `cluster.x-k8s.io/v1beta2`. Rancher backup files include Cluster API CRDs. When restoring backup data from Rancher v2.13.x to a local cluster after upgrading to v2.14.0, the Rancher Backup application first restores the v1beta1 CRDs. This fails because the v1beta2 version cannot be removed from the CRDs while v1beta2 custom resources are present in the cluster. + ### Step 1: Clean Up the Upstream (Local) Cluster To avoid rollback failure, follow these [instructions](https://github.com/rancher/rancher-cleanup/blob/main/README.md) to run the scripts **before** you attempt a restore operation or rollback: diff --git a/versioned_docs/version-2.13/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md b/versioned_docs/version-2.13/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md index 939522101ea..114edc243ec 100644 --- a/versioned_docs/version-2.13/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md +++ b/versioned_docs/version-2.13/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md @@ -19,6 +19,7 @@ In order to deploy and run the adapter successfully, you need to ensure its vers | Rancher Version | Adapter Version | |-----------------|------------------| +| v2.13.4 | 108.0.0+up8.0.0 | | v2.13.3 | 108.0.0+up8.0.0 | | v2.13.2 | 108.0.0+up8.0.0 | | v2.13.1 | 108.0.0+up8.0.0 | diff --git a/versioned_docs/version-2.13/reference-guides/rancher-webhook.md b/versioned_docs/version-2.13/reference-guides/rancher-webhook.md index 9b8206fb9dc..cca617cbb0a 100644 --- a/versioned_docs/version-2.13/reference-guides/rancher-webhook.md +++ b/versioned_docs/version-2.13/reference-guides/rancher-webhook.md @@ -20,6 +20,7 @@ Each Rancher version is designed to be compatible with a single version of the w | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| +| v2.13.4 | v0.9.3 | ✓ | ✗ | | v2.13.3 | v0.9.3 | ✓ | ✓ | | v2.13.2 | v0.9.2 | ✓ | ✓ | | v2.13.1 | v0.9.1 | ✓ | ✓ | diff --git a/versioned_docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md b/versioned_docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md index 1845618a5bf..0d9305f1144 100644 --- a/versioned_docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md +++ b/versioned_docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md @@ -24,11 +24,14 @@ Follow the instructions from this page when: Alternative steps need to be performed for rollbacks in the following scenarios: - Rolling back from v2.6.4 and later to an earlier version of v2.6.x. - Rolling back from v2.7.7 and later to an earlier version of v2.7.x. +- Rolling back from v2.14.0 and later to an earlier version of v2.13.x. In Rancher v2.6.4, the cluster-api module is upgraded from v0.4.4 to v1.0.2. The cluster-api v1.0.2, in turn, upgrades the apiVersions of its Custom Resource Definitions (CRDs) from `cluster.x-k8s.io/v1alpha4` to `cluster.x-k8s.io/v1beta1`. Custom Resources (CRs) that use the older apiVersion (v1alpha4) are incompatible with v1beta1, which causes rollbacks to fail when you attempt to move from Rancher v2.6.4 to any previous version of Rancher v2.6.x. In Rancher v2.7.7, the app `rancher-provisioning-capi` is installed on the upstream (local) cluster automatically as a replacement for the embedded cluster-api controllers. Conflicts and unexpected errors will occur if the upstream cluster contains both the app, and Rancher v2.7.6 and earlier. Therefore, alternative steps are needed if you attempt to move from Rancher v2.7.7 to any previous version of Rancher v2.7.x. +In Rancher v2.14.0, the cluster-api module is upgraded from v1.10.6 to v1.12.2. The cluster-api v1.12.2, in turn, upgrades the apiVersions of its Custom Resource Definitions (CRDs) from `cluster.x-k8s.io/v1beta1` to `cluster.x-k8s.io/v1beta2`. Rancher backup files include Cluster API CRDs. When restoring backup data from Rancher v2.13.x to a local cluster after upgrading to v2.14.0, the Rancher Backup application first restores the v1beta1 CRDs. This fails because the v1beta2 version cannot be removed from the CRDs while v1beta2 custom resources are present in the cluster. + ### Step 1: Clean Up the Upstream (Local) Cluster To avoid rollback failure, follow these [instructions](https://github.com/rancher/rancher-cleanup/blob/main/README.md) to run the scripts **before** you attempt a restore operation or rollback: