Merge pull request #69688 from kquinn1204/OCPBUGS-25811-415

Author: aireilly

modules/cnf-deploying-the-numa-aware-scheduler.adoc

@@ -8,7 +8,7 @@
 
 After you install the NUMA Resources Operator, do the following to deploy the NUMA-aware secondary pod scheduler:
 
-* Configure the performance profile. 
+* Configure the performance profile.
 
 * Deploy the NUMA-aware secondary scheduler.
 
@@ -36,8 +36,8 @@ metadata:
   name: perfprof-nrop
 spec:
   cpu: <1>
-    isolated: "4-51,56-103" 
-    reserved: "0,1,2,3,52,53,54,55" 
+    isolated: "4-51,56-103"
+    reserved: "0,1,2,3,52,53,54,55"
   nodeSelector:
     node-role.kubernetes.io/worker: ""
   numa:
@@ -69,8 +69,8 @@ kind: NUMAResourcesScheduler
 metadata:
   name: numaresourcesscheduler
 spec:
-  imageSpec: "registry.redhat.io/openshift4/noderesourcetopology-scheduler-container-rhel8:v{product-version}"
-  cacheResyncPeriod: "5s" <1> 
+  imageSpec: "registry.redhat.io/openshift4/noderesourcetopology-scheduler-rhel9:v{product-version}"
+  cacheResyncPeriod: "5s" <1>
 ----
 <1> Enter an interval value in seconds for synchronization of the scheduler cache. A value of `5s` is typical for most implementations.
 +