From 2f4a258f711941a526102e18ea53aedd39bfe75e Mon Sep 17 00:00:00 2001 From: Kevin Quinn Date: Tue, 4 Feb 2025 15:12:12 +0000 Subject: [PATCH] TELCODOCS-2051 NUMA-aware scheduling: clarify the operator configuration --- modules/cnf-creating-nrop-cr.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/cnf-creating-nrop-cr.adoc b/modules/cnf-creating-nrop-cr.adoc index 598e7b4d6d..d53143f378 100644 --- a/modules/cnf-creating-nrop-cr.adoc +++ b/modules/cnf-creating-nrop-cr.adoc @@ -33,7 +33,7 @@ spec: pools.operator.machineconfiguration.openshift.io/worker: "" <1> ---- + -<1> This should match the `MachineConfigPool` that you want to configure the NUMA Resources Operator on. For example, you might have created a `MachineConfigPool` named `worker-cnf` that designates a set of nodes expected to run telecommunications workloads. +<1> This must match the `MachineConfigPool` resource that you want to configure the NUMA Resources Operator on. For example, you might have created a `MachineConfigPool` resource named `worker-cnf` that designates a set of nodes expected to run telecommunications workloads. Each `NodeGroup` must match exactly one `MachineConfigPool`. Configurations where `NodeGroup` matches more than one `MachineConfigPool` are not supported. .. Create the `NUMAResourcesOperator` CR by running the following command: +