openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 15:46:57 +01:00
Code Issues Releases Activity

Tweaks for MachineSet infra management for clarity

Browse Source
This commit is contained in:
Cody Hoag
2021-01-21 10:50:36 -05:00
committed by openshift-cherrypick-robot
parent 0834ce61c9
commit 4fa440b6ea
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
machine_management/creating-infrastructure-machinesets.adoc
View File

@@ -47,9 +47,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]