Add RKE1 EOL information (#723)

bk201 · jillian-maroket · web-flow · commit e62dc64ba80e · 2025-03-10T12:26:37.000+08:00
* Add RKE1 EOL information

Signed-off-by: Kiefer Chang &lt;kiefer.chang@suse.com&gt;
Co-authored-by: Jillian Maroket &lt;67180770+jillian-maroket@users.noreply.github.com&gt;
diff --git a/docs/rancher/cloud-provider.md b/docs/rancher/cloud-provider.md
@@ -63,6 +63,15 @@ To eliminate the need for manual intervention after the guest cluster is provisi
 :::
 
 ### Deploying to the RKE1 Cluster with Harvester Node Driver
+
+:::caution
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Switching to RKE2, which provides a more secure and efficient environment, is recommended.
+
+In-place upgrades are not an option, so you must [create new RKE2 clusters](./node/rke2-cluster.md) and migrate the workloads from your existing RKE clusters (known as replatforming). For more information, see [RKE End of Life](https://www.suse.com/support/kb/doc/?id=000021513).
+
+:::
+
 When spinning up an RKE cluster using the Harvester node driver, you can perform two steps to deploy the `Harvester` cloud provider:
 
 1. Select `Harvester(Out-of-tree)` option.
diff --git a/docs/rancher/csi-driver.md b/docs/rancher/csi-driver.md
@@ -44,6 +44,14 @@ Currently, the Harvester CSI driver only supports single-node read-write(RWO) vo
 
 ### Deploying with Harvester RKE1 node driver
 
+:::caution
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Switching to RKE2, which provides a more secure and efficient environment, is recommended.
+
+In-place upgrades are not an option, so you must [create new RKE2 clusters](./node/rke2-cluster.md) and migrate the workloads from your existing RKE clusters (known as replatforming). For more information, see [RKE End of Life](https://www.suse.com/support/kb/doc/?id=000021513).
+
+:::
+
 - Select the `Harvester(Out-of-tree)` option.
 
     ![](/img/v1.2/rancher/rke-cloud-provider.png)
diff --git a/docs/rancher/node/rke1-cluster.md b/docs/rancher/node/rke1-cluster.md
@@ -8,6 +8,14 @@ title: "Creating an RKE1 Kubernetes Cluster"
   <link rel="canonical" href="https://docs.harvesterhci.io/v1.4/rancher/node/rke1-cluster"/>
 </head>
 
+:::caution
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Switching to RKE2, which provides a more secure and efficient environment, is recommended.
+
+In-place upgrades are not an option, so you must [create new RKE2 clusters](./rke2-cluster.md) and migrate the workloads from your existing RKE clusters (known as replatforming). For more information, see [RKE End of Life](https://www.suse.com/support/kb/doc/?id=000021513).
+
+:::
+
 You can now provision RKE1 Kubernetes clusters on top of the Harvester cluster in Rancher using the built-in Harvester node driver.
 
 RKE1 and RKE2 have several slight behavioral differences. Refer to the [differences between RKE1 and RKE2](https://ranchermanager.docs.rancher.com/v2.7/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences) to get some high-level insights.
diff --git a/versioned_docs/version-v1.3/rancher/cloud-provider.md b/versioned_docs/version-v1.3/rancher/cloud-provider.md
@@ -63,6 +63,15 @@ To eliminate the need for manual intervention after the guest cluster is provisi
 :::
 
 ### Deploying to the RKE1 Cluster with Harvester Node Driver
+
+:::caution
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Switching to RKE2, which provides a more secure and efficient environment, is recommended.
+
+In-place upgrades are not an option, so you must [create new RKE2 clusters](./node/rke2-cluster.md) and migrate the workloads from your existing RKE clusters (known as replatforming). For more information, see [RKE End of Life](https://www.suse.com/support/kb/doc/?id=000021513).
+
+:::
+
 When spinning up an RKE cluster using the Harvester node driver, you can perform two steps to deploy the `Harvester` cloud provider:
 
 1. Select `Harvester(Out-of-tree)` option.
diff --git a/versioned_docs/version-v1.3/rancher/csi-driver.md b/versioned_docs/version-v1.3/rancher/csi-driver.md
@@ -49,6 +49,14 @@ Currently, the Harvester CSI driver only supports single-node read-write(RWO) vo
 
 ### Deploying with Harvester RKE1 node driver
 
+:::caution
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Switching to RKE2, which provides a more secure and efficient environment, is recommended.
+
+In-place upgrades are not an option, so you must [create new RKE2 clusters](./node/rke2-cluster.md) and migrate the workloads from your existing RKE clusters (known as replatforming). For more information, see [RKE End of Life](https://www.suse.com/support/kb/doc/?id=000021513).
+
+:::
+
 - Select the `Harvester(Out-of-tree)` option.
 
     ![](/img/v1.2/rancher/rke-cloud-provider.png)
diff --git a/versioned_docs/version-v1.3/rancher/node/rke1-cluster.md b/versioned_docs/version-v1.3/rancher/node/rke1-cluster.md
@@ -7,6 +7,13 @@ title: "Creating an RKE1 Kubernetes Cluster"
 <head>
   <link rel="canonical" href="https://docs.harvesterhci.io/v1.1/rancher/node/rke1-cluster"/>
 </head>
+:::caution
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Switching to RKE2, which provides a more secure and efficient environment, is recommended.
+
+In-place upgrades are not an option, so you must [create new RKE2 clusters](./rke2-cluster.md) and migrate the workloads from your existing RKE clusters (known as replatforming). For more information, see [RKE End of Life](https://www.suse.com/support/kb/doc/?id=000021513).
+
+:::
 
 You can now provision RKE1 Kubernetes clusters on top of the Harvester cluster in Rancher using the built-in Harvester node driver.
 
diff --git a/versioned_docs/version-v1.4/rancher/cloud-provider.md b/versioned_docs/version-v1.4/rancher/cloud-provider.md
@@ -63,6 +63,15 @@ To eliminate the need for manual intervention after the guest cluster is provisi
 :::
 
 ### Deploying to the RKE1 Cluster with Harvester Node Driver
+
+:::caution
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Switching to RKE2, which provides a more secure and efficient environment, is recommended.
+
+In-place upgrades are not an option, so you must [create new RKE2 clusters](./node/rke2-cluster.md) and migrate the workloads from your existing RKE clusters (known as replatforming). For more information, see [RKE End of Life](https://www.suse.com/support/kb/doc/?id=000021513).
+
+:::
+
 When spinning up an RKE cluster using the Harvester node driver, you can perform two steps to deploy the `Harvester` cloud provider:
 
 1. Select `Harvester(Out-of-tree)` option.
diff --git a/versioned_docs/version-v1.4/rancher/csi-driver.md b/versioned_docs/version-v1.4/rancher/csi-driver.md
@@ -44,6 +44,14 @@ Currently, the Harvester CSI driver only supports single-node read-write(RWO) vo
 
 ### Deploying with Harvester RKE1 node driver
 
+:::caution
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Switching to RKE2, which provides a more secure and efficient environment, is recommended.
+
+In-place upgrades are not an option, so you must [create new RKE2 clusters](./node/rke2-cluster.md) and migrate the workloads from your existing RKE clusters (known as replatforming). For more information, see [RKE End of Life](https://www.suse.com/support/kb/doc/?id=000021513).
+
+:::
+
 - Select the `Harvester(Out-of-tree)` option.
 
     ![](/img/v1.2/rancher/rke-cloud-provider.png)
diff --git a/versioned_docs/version-v1.4/rancher/node/rke1-cluster.md b/versioned_docs/version-v1.4/rancher/node/rke1-cluster.md
@@ -8,6 +8,14 @@ title: "Creating an RKE1 Kubernetes Cluster"
   <link rel="canonical" href="https://docs.harvesterhci.io/v1.4/rancher/node/rke1-cluster"/>
 </head>
 
+:::caution
+
+Rancher Kubernetes Engine (RKE) will reach the end of its life on **July 31, 2025**. Harvester **v1.6.0** and later versions will not support RKE. Switching to RKE2, which provides a more secure and efficient environment, is recommended.
+
+In-place upgrades are not an option, so you must [create new RKE2 clusters](./rke2-cluster.md) and migrate the workloads from your existing RKE clusters (known as replatforming). For more information, see [RKE End of Life](https://www.suse.com/support/kb/doc/?id=000021513).
+
+:::
+
 You can now provision RKE1 Kubernetes clusters on top of the Harvester cluster in Rancher using the built-in Harvester node driver.
 
 RKE1 and RKE2 have several slight behavioral differences. Refer to the [differences between RKE1 and RKE2](https://ranchermanager.docs.rancher.com/v2.7/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences) to get some high-level insights.
