OCPBUGS#66951 and 66955: Update 4.19.10 RNs for OLM NP support

Author: michaelryanpeter

release_notes/ocp-4-19-release-notes.adoc

@@ -3296,6 +3296,16 @@ $ oc adm release info 4.19.10 --pullspecs
 
 * The name of the `MachineOSConfig` object used with {image-mode-os-on-lower} must now be the same as the machine config pool where you want to deploy the custom layered image. This change prevents using multiple `MachineOSConfig` objects with each machine config pool. (link:https://issues.redhat.com/browse/OCPBUGS-60414[OCPBUGS-60414])
 
+:olm-np-z: 10
+* {empty}
++
+--
+include::snippets/olmv0-and-v1-rn-np-support.adoc[]
+--
+(link:https://issues.redhat.com/browse/OCPBUGS-60525[OCPBUGS-60525] and link:https://issues.redhat.com/browse/OCPBUGS-60521[OCPBUGS-60521])
+
+:!olm-np-z:
+
 [id="ocp-4-19-10-bug-fixes_{context}"]
 ==== Bug fixes
 

snippets/olmv0-and-v1-rn-np-support.adoc

@@ -17,7 +17,7 @@ If your current version of OLM does not support tailored network policies, a not
 * The {hybrid-console}
 * The web console of the affected cluster
 
-Update to {product-title} {product-version}.{olm-np-z-stream} or later to enable OLM support for tailored network policies.
+Update to {product-title} {product-version}.{olm-np-z} or later to enable OLM support for tailored network policies.
 ====
 
 For more information, including the planned timeline for releasing Red Hat-provided Operators with tailored network policies, see link:https://access.redhat.com/articles/7133113[Operators shipping with network policies may require OCP cluster upgrade before they can be upgraded (Red Hat Knowledgebase)].