OSDOCS-20245:Update the z-stream RNs for 4.22.2

modules/zstream-4-22-2.adoc

@@ -0,0 +1,37 @@
+// Module included in the following assemblies:
+//
+// * release_notes/ocp-4-22-release-notes.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="zstream-4-22-2_{context}"]
+= RHSA-2026:27009 - {product-title} {product-version}.2 fixed issues and security update
+
+Issued: 16 June 2026
+
+[role="_abstract"]
+{product-title} release {product-version}.2 is now available. The list of fixed issues that are included in the update is documented in the link:https://access.redhat.com/errata/RHSA-2026:27009[RHSA-2026:27009] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2026:27007[RHBA-2026:27007] advisory.
+
+Space precluded documenting all of the container images for this release in the advisory.
+
+You can view the container images in this release by running the following command:
+
+[source,terminal]
+----
+$ oc adm release info 4.22.2 --pullspecs
+----
+
+[id="zstream-4-22-2-fixed-issues_{context}"]
+== Fixed issues
+
+* Before this update, when you created a namespace-scoped `ProjectHelmChartRepository` object in the {product-title} web console, the Certificate Authority (CA) certificate and Transport Layer Security (TLS) client config drop-down menus listed only the resources from the `openshift-config` namespace. With this release, the form lists CA and TLS resources from the selected project namespace for `ProjectHelmChartRepository` objects, while cluster-scoped `HelmChartRepository` objects continue to use the `openshift-config` namespace. (link:https://redhat.atlassian.net/browse/OCPBUGS-76328[OCPBUGS-76328])
+
+* Before this update, when a boundary clock (T-BC) entered holdover, the `event.sync.sync-status.synchronization-state-change` (/sync/sync-status/sync-state) event would sometimes incorrectly report `FREERUN` instead of `HOLDOVER`. These reports might have occurred because of an issue with the calculation of the overall node sync state. With this release, the `ptp4l` state is ignored. As a result, the `event.sync.sync-status.synchronization-state-change` (/sync/sync-status/sync-state) event correctly reports `HOLDOVER`. (link:https://redhat.atlassian.net/browse/OCPBUGS-86530[OCPBUGS-86530])
+
+* Before this update, arbiter configs previously used runc as the default container runtime. With this release, the arbiter configs have been updated to be in sync with the master nodes and use crun as the default container runtime. (link:https://redhat.atlassian.net/browse/OCPBUGS-87019[OCPBUGS-87019])
+
+* Before this update, the `openshift-apiserver` might have failed when multiple requests accessed project authorization data at the same time. This issue occurred more often on clusters with many namespaces and role-based access control (RBAC) rules. As a consequence, `openshift-apiserver` pods restarted unexpectedly with exit code `2`, which temporarily disrupted the API availability for project and namespace operations. With this release, the project authorization cache safely handles concurrent access. As a result, the `openshift-apiserver` namespace does not fail during concurrent project authorization lookups, and project listing operations remain responsive regardless of cluster size. (link:https://redhat.atlassian.net/browse/OCPBUGS-87022[OCPBUGS-87022])
+
+[id="zstream-4-22-2-updating_{context}"]
+== Updating
+
+To update an {product-title} 4.22 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI].Expand comment

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

@@ -44,3 +44,6 @@ include::modules/rn-ocp-release-notes-known-issues.adoc[leveloffset=+1]
 // Asynchronous errata updates
 include::modules/rn-ocp-release-notes-async-errata-updates.adoc[leveloffset=+1]
 
+// zstream 4.22.2 RNs full document
+include::modules/zstream-4-22-2.adoc[leveloffset=+2]
+