From a31e4e8eb9e058a097104640a5cb03edaf9f5851 Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Fri, 11 Mar 2022 18:43:27 -0500 Subject: [PATCH] Updated per feedback --- .../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 94e2c64bfb4..8b739dfed4a 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 @@ -21,7 +21,7 @@ The following are some specific example configuration changes that may cause the - When editing the cluster and enabling `drain before delete`, the existing control plane nodes and worker are deleted and new nodes are created. -- When nodes are being provisioned, performing a scale down operation may result in both nodes getting deleted and a new one being provisioned. +- When nodes are being provisioned, performing a scale down operation may, in some cases, result in both nodes getting deleted and a new one being provisioned. Users who are used to RKE1 provisioning should take note of this new RKE2 behavior which may be unexpected.