From 6d6b9a6110540a84a943943999f8d37d8b484ca8 Mon Sep 17 00:00:00 2001 From: swope Date: Mon, 2 Dec 2024 14:26:36 -0500 Subject: [PATCH] Update config_infra_nodes.adoc --- install/config_infra_nodes.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/install/config_infra_nodes.adoc b/install/config_infra_nodes.adoc index 8bc152510b..f34a09e64e 100644 --- a/install/config_infra_nodes.adoc +++ b/install/config_infra_nodes.adoc @@ -8,9 +8,9 @@ After adding infrastructure nodes to your {ocp-short} cluster, follow the xref:. [#config-infra-nodes-ocp] == Configuring infrastructure nodes to the {ocp-short} cluster -Follow the procedures that are described in link:https://docs.redhat.com/documentation/en-us/openshift_container_platform/4.15/html/machine_management/creating-infrastructure-machinesets[Creating infrastructure machine sets] in the {ocp-short} documentation. Infrastructure nodes are configured with a Kubernetes `taint` and `label` to keep non-management workloads from running on them. +Follow the procedures that are described in link:https://docs.redhat.com/documentation/en-us/openshift_container_platform/4.15/html/machine_management/creating-infrastructure-machinesets[Creating infrastructure machine sets] in the {ocp-short} documentation. Infrastructure nodes are configured with a Kubernetes `taints` and `labels` to keep non-management workloads from running on them. -. To be compatible with the infrastructure node enablement provided by {acm-short}, ensure your infrastructure nodes have the following `taint` and `label` applied: +. To be compatible with the infrastructure node enablement provided by {acm-short}, ensure your infrastructure nodes have the following `taints` and `labels` applied: + [source,yaml]