OSDOCS-14545: Documented the 4.17.28 z-stream RNs

Author: dfitzmau

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

@@ -2884,6 +2884,40 @@ This section will continue to be updated over time to provide notes on enhanceme
 For any {product-title} release, always review the instructions on xref:../updating/updating_a_cluster/updating-cluster-web-console.adoc#updating-cluster-web-console[updating your cluster] properly.
 ====
 
+// 4.17.28
+[id="ocp-4-17-28_{context}"]
+=== RHSA-2025:4431 - {product-title} {product-version}.28 bug fix and security update advisory
+
+Issued: 8 May 2025
+
+{product-title} release {product-version}.28 is now available. The list of bug fixes that are included in the update is documented in the link:https://access.redhat.com/errata/RHSA-2025:4431[RHSA-2025:4431] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:4433[RHBA-2025:4433] 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.17.28 --pullspecs
+----
+
+[id="ocp-4-17-28-bug-fixes_{context}"]
+==== Bug fixes
+
+* Previously, if you had permission to view nodes but not Certificate Signing Requests (CSR), you could not access the *Nodes list* page. With this release, permissions to view CSRs are no longer required to access the *Nodes list* page. (link:https://issues.redhat.com/browse/OCPBUGS-55202[*OCPBUGS-55202*])
+
+* Previously, after you deleted the `ClusterResourceOverride` custom resource (CR) or you uninstalled the Cluster Resource Override Operator, which also removes the object, the `v1.admission.autoscaling.openshift.io` API service becomes unreachable. This situation impacted other cluster functions, such as other Operator installations from succeeding. With this release, when you delete the Cluster Resource Override Operator, the `v1.admission.autoscaling.openshift.io` API service is also removed. As a result, you can now install other Operators without experiencing installation failures. (link:https://issues.redhat.com/browse/OCPBUGS-55355[*OCPBUGS-55355*])
+
+* Previously, when you attempted to upgrade the Cluster Resource Override Operator from {product-title} 4.16 to {product-version}, the Cluster Resource Override webhook stopped functioning. This situation prevented pods from getting created in namespaces that had the Cluster Resource Override enabled. With this release, a stale secret is deleted so that {product-title} regenerates the secret with the correct parameters and values during an upgrade operation. As a result, the Operator upgrade succeeds and you can now create pods in any namespaces that have the Cluster Resource Override enabled. (link:https://issues.redhat.com/browse/OCPBUGS-55239[*OCPBUGS-55239*])
+
+* Previously, during Fibre Channel multipath disk discovery, the Assisted Installer failed to include World Wide Name (WWN) details in the configuration for a cluster. As a result, a Fibre Channel multipath disk could not be matched with a WWN root device. This means that when you specified a `wwn` root device hint in your cluster configuration, the hint excluded all Fibre Channel multipath disks. With this release, the Assisted Installer now includes WWN details in the configuration for a cluster during Fibre Channel multipath disk discovery. If multiple Fibre Channel multipath disks exist, you can now effectively use the `wwn` root device hint to choose a primary disk for your cluster. (link:https://issues.redhat.com/browse/OCPBUGS-55184[*OCPBUGS-55184*]) 
+
+* Previously, the `mtu-migration` service did not work correctly when you used `nmstate` to manage a `br-ex` bridge because of a missing service dependency. With this release, the service dependency is now added so that a network configuration that uses `nmstate` to manage a `br-ex` is correct before the migration process begins. (link:https://issues.redhat.com/browse/OCPBUGS-54830[*OCPBUGS-54830*])
+
+[id="ocp-4-17-28-updating_{context}"]
+==== Updating
+To update an {product-title} 4.17 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI].
+
 // 4.17.27
 [id="ocp-4-17-27_{context}"]
 === RHSA-2025:4204 - {product-title} {product-version}.27 bug fix and security update advisory