From 9ac537112475b17ac108c3e2f49ae9bc1199f96c Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Wed, 24 May 2023 10:06:07 -0700 Subject: [PATCH] Update versioned_docs/version-2.6/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences.md Co-authored-by: Marty Hernandez Avedon --- .../launch-kubernetes-with-rancher/rke1-vs-rke2-differences.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-2.6/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences.md b/versioned_docs/version-2.6/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences.md index cf3c4f4b93f..be09fe66c69 100644 --- a/versioned_docs/version-2.6/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences.md +++ b/versioned_docs/version-2.6/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences.md @@ -20,7 +20,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. -- For Rancher v2.6.6 and earlier, when nodes are being provisioned and a scale down operation is performed, rather than scaling down the desired number of nodes, it is possible that the currently provisioning nodes get deleted and new nodes are provisioned to reach the desired node count. Please note that this is a bug in Cluster API, and it will be fixed in an upcoming release. Once fixed, Rancher will update the documentation. +- For Rancher v2.6.6 and earlier, when nodes are being provisioned and a scale down operation is performed, rather than scaling down the desired number of nodes, it is possible that the currently provisioning nodes get deleted and new nodes are provisioned to reach the desired node count. Please note that this is a bug in the Cluster API, and that it will be fixed in an upcoming release. Once fixed, Rancher will update the documentation. Users who are used to RKE1 provisioning should take note of this new RKE2 behavior which may be unexpected.