From 808f0994aabcec244a364319cc000e2a270b27a7 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 30 Aug 2021 14:03:37 -0700 Subject: [PATCH] Update content/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/_index.md Co-authored-by: Derek Nola --- .../en/cluster-provisioning/rke-clusters/node-pools/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/_index.md b/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/_index.md index 08688febf92..6745cb34c81 100644 --- a/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/_index.md +++ b/content/rancher/v2.6/en/cluster-provisioning/rke-clusters/node-pools/_index.md @@ -140,7 +140,7 @@ If you don't find the node driver that you want to use, you can see if it is ava The RKE2 CLI has two roles, `server` and `agent`. RKE2 CLI was designed not to expose node roles as a first-class concept. After RKE2 was fully integrated into Rancher v2.6, RKE2 node pools can use `etcd`, `controlplane` or `worker` roles within Rancher. -The same functionality of using `etcd`, `controlplane` and `worker` nodes is possible in the RKE2 CLI by using flags and node tainting to control where workloads and the Kubernetes master were scheduled. The reason those roles were not implemented as first-class roles in the RKE CLI is that RKE2 is conceptualized as a set of raw building blocks that are best leveraged through an orchestration system such as Rancher. +The same functionality of using `etcd`, `controlplane` and `worker` nodes is possible in the RKE2 CLI by using flags and node tainting to control where workloads and the Kubernetes master were scheduled. The reason those roles were not implemented as first-class roles in the RKE2 CLI is that RKE2 is conceptualized as a set of raw building blocks that are best leveraged through an orchestration system such as Rancher. In our [recommended cluster architecture]({{}}/rancher/v2.6/en/cluster-provisioning/production/recommended-architecture/), we outline how many nodes of each role clusters should have: