From 2d252669a392ed444f6d8e9d61123abcaa373571 Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Fri, 11 Mar 2022 18:36:11 -0500 Subject: [PATCH] Updated per feedback --- .../behavior-differences-between-rke1-and-rke2/_index.md | 6 ++++++ 1 file changed, 6 insertions(+) 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 bc0e1134ec4..94e2c64bfb4 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 @@ -17,6 +17,12 @@ RKE2/K3s provisioning is built on top of the Cluster API (CAPI) upstream framewo 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. +The following are some specific example configuration changes that may cause the described behavior: + +- 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. + Users who are used to RKE1 provisioning should take note of this new RKE2 behavior which may be unexpected. ### Terminology