OCPBUGS#66952 and 66951: Update 4.18.23 RNs for OLM NP support

Author: michaelryanpeter

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

@@ -3328,6 +3328,16 @@ $ oc adm release info 4.18.23 --pullspecs
 [id="ocp-4-18-23-enhancements_{context}"]
 ==== Enhancements
 
+:olm-np-z: 23
+* {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:
+
 * Before this update, deleting an `istag` resource with the `--dry-run=server` option unintentionally caused actual deletion of the image from the server. This unexpected deletion occurred due to the dry-run option being implemented incorrectly in the `oc delete istag` command. With this release, the `dry-run` option is wired to the 'oc delete istag' command. As a result, the accidental deletion of image objects is prevented and the `istag` object remains intact when using the `--dry-run=server` option. (link:https://issues.redhat.com/browse/OCPBUGS-58461[OCPBUGS-58461])
 
 * Before this update, the `cluster-policy-controller` container was exposing the `10357` port for all networks (the bind address was set to `0.0.0.0`). The port was exposed outside the host network for the node because the KCM pod manifest set `hostNetwork` to `true`. This port is used solely for the probe of the container. With this enhancement, the bind address was updated to listen on the `localhost` only. As result, the node security is improved because the port is not exposed outside the node network. (link:https://issues.redhat.com/browse/OCPBUGS-60131[OCPBUGS-60131])

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)].