Merge pull request #88631 from dfitzmau/OSDOCS-13377

OSDOCS-13377: Documented the 4.17.17 z-stream notes

Author: dfitzmau

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

@@ -2874,6 +2874,49 @@ 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.17
+[id="ocp-4-17-17_{context}"]
+=== RHSA-2025:1403 - {product-title} {product-version}.17 bug fix, and security update advisory
+
+Issued: 18 February 2025
+
+{product-title} release {product-version}.17 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:1403[RHSA-2025:1403] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:1405[RHBA-2025:1405] 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.17 --pullspecs
+----
+
+[id="ocp-4-17-17-bug-fixes_{context}"]
+==== Bug fixes
+
+* Previously, the availability set fault domain count was hardcoded to `2`. This value works in most regions on {azure-first} because the fault domain counts are typically at least `2`, but failed in the `centraluseuap` and `eastusstg` regions. With this release, the availability set fault domain count in a region is set dynamically so that this issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-50017[*OCPBUGS-50017*])
+
+* Previously, when installing a cluster on {gcp-first}, a cluster installation failed when an instance required IP Forwarding to be disabled. With this release, IP Forwarding is disabled for all {gcp-short} machines before cluster installation so that the cluster installation issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-49993[*OCPBUGS-49993*])
+
+// SME
+* Previously, you could not install an cluster on {aws-short} in the `ap-southeast-5` region or other regions because the {product-title} internal registry did not support these regions. With this release, the internal registry is updated to include the following regions so that this issue no longer occurs:
++
+** `ap-southeast-5`
+** `ap-southeast-7`
+** `ca-west-1`
+** `il-central-1`
+** `mx-central-1`
++
+(link:https://issues.redhat.com/browse/OCPBUGS-49695[*OCPBUGS-49695*])
+
+* Previously, when a pod was running on a node on which egress IPv6 is assigned, the pod was not able to communicate with the Kubernetes service in a dual-stack cluster. This resulted in traffic with the IP family, that the `egressIP` object is not applicable to, being dropped. With this release, only the source network address translation (SNAT) for the IP family that the egress IP applied to is deleted, eliminating the risk of traffic being dropped. (link:https://issues.redhat.com/browse/OCPBUGS-48828[*OCPBUGS-48828*])
+
+* Previously, when you attempted to use the {hcp} CLI to create a cluster in a disconnected environment, the installation command failed. An issue existed with the registry that hosts the command. With this release, a fix to the command registry means that you can use the {hcp} CLI to create a cluster in a disconnected environment. (link:https://issues.redhat.com/browse/OCPBUGS-48170[*OCPBUGS-48170*])
+
+[id="ocp-4-17-17-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.16
 [id="ocp-4-17-16_{context}"]
 === RHSA-2025:1120 - {product-title} {product-version}.16 bug fix, and security update advisory