From e0c67823c9e7a7c8b706208f6677c967f71c23ad Mon Sep 17 00:00:00 2001 From: Cody Hoag Date: Thu, 21 Jan 2021 10:50:36 -0500 Subject: [PATCH] Tweaks for MachineSet infra management for clarity --- machine_management/creating-infrastructure-machinesets.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/machine_management/creating-infrastructure-machinesets.adoc b/machine_management/creating-infrastructure-machinesets.adoc index db26d44f3e..d1fbc72159 100644 --- a/machine_management/creating-infrastructure-machinesets.adoc +++ b/machine_management/creating-infrastructure-machinesets.adoc @@ -45,9 +45,9 @@ include::modules/machineset-creating.adoc[leveloffset=+2] [id="assigning-machineset-resources-to-infra-nodes"] == Assigning machine set resources to infrastructure nodes -After creating an infrastructure machine set, the `worker` and `infra` roles are applied to new infra nodes. The `worker` role is required for infra nodes during startup. Nodes with the `infra` role applied are not counted toward the total number of subscriptions that are required to run the environment, even when the `worker` role is also applied. +After creating an infrastructure machine set, the `worker` and `infra` roles are applied to new infra nodes. Nodes with the `infra` role applied are not counted toward the total number of subscriptions that are required to run the environment, even when the `worker` role is also applied. -However, with an infra node being assigned as a worker, there is a chance user workloads could get inadvertently assigned to an infra node. To avoid this, you must apply a taint to the infra node and tolerations for the pods you want to control. +However, with an infra node being assigned as a worker, there is a chance user workloads could get inadvertently assigned to an infra node. To avoid this, you can apply a taint to the infra node and tolerations for the pods you want to control. include::modules/binding-infra-node-workloads-using-taints-tolerations.adoc[leveloffset=+2]