From 7cf2e83c27089160fcfeb6c0f78ef54cc95b767e Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Fri, 11 Mar 2022 18:25:08 -0500 Subject: [PATCH] Emphasizing reprovisioning may occur --- .../behavior-differences-between-rke1-and-rke2/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/behavior-differences-between-rke1-and-rke2/_index.md b/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/behavior-differences-between-rke1-and-rke2/_index.md index e530f5abc17..bc0e1134ec4 100644 --- a/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/behavior-differences-between-rke1-and-rke2/_index.md +++ b/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/behavior-differences-between-rke1-and-rke2/_index.md @@ -15,7 +15,7 @@ RKE1 uses Docker for deploying and managing control plane components and the con RKE2/K3s provisioning is built on top of the Cluster API (CAPI) upstream framework which often makes RKE2-provisioned clusters behave differently than RKE1-provisioned clusters. -When you make changes to your cluster configuration in RKE2, this may result in nodes reprovisioning. This is controlled by CAPI controllers and not by Rancher itself. Note that for etcd nodes, the same behavior does not apply. +When you make changes to your cluster configuration in RKE2, this **may** result in nodes reprovisioning. This is controlled by CAPI controllers and not by Rancher itself. Note that for etcd nodes, the same behavior does not apply. Users who are used to RKE1 provisioning should take note of this new RKE2 behavior which may be unexpected.