Managing an upgrade to OpenShift 4.18 or later for a cluster with an existing NUMA-aware scheduler configuration
Updated -
From OpenShift 4.18, the NUMA Resources Operator no longer creates a custom SELinux policy to enable the installation of Operator components on a target node. Instead, the Operator uses a built-in container SELinux policy. This change removes the additional node reboot that was required when installing the Operator in earlier versions of OpenShift.
However, in clusters with an existing ...
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
