Merge pull request #58056 from mburke5678/nodes-cro-changes-module-413

OSDOCS-5348: 4.13 Module to Automate workaround for SELinux relabeling issue for large volumes

Author: mburke5678

modules/nodes-pods-configuring-reducing.adoc

@@ -17,6 +17,8 @@ You can reduce this delay by applying one of the following workarounds:
 
 * Use the `fsGroupChangePolicy` field inside an SCC to control the way that {product-title} checks and manages ownership and permissions for a volume.
 
+* Use the Cluster Resource Override Operator to automatically apply an SCC to skip the SELinux relabeling.
+
 * Use a runtime class to skip the SELinux relabeling for a volume.
 
 For information, see link:https://access.redhat.com/solutions/6221251[When using Persistent Volumes with high file counts in OpenShift, why do pods fail to start or take an excessive amount of time to achieve "Ready" state?].