Merge pull request #100772 from wgabor0427/OSDOCS-15026

kalexand-rh · web-flow · commit c9cd10e77bc1 · 2025-10-17T17:31:14.000-04:00
OSDOCS-15026 commenting out unused sections
diff --git a/release_notes/ocp-4-20-release-notes.adoc b/release_notes/ocp-4-20-release-notes.adoc
@@ -58,11 +58,11 @@ Before this update, the self-signed loopback certificate for the Kubernetes API
 
 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.
 
-[id="ocp-release-notes-auth_{context}"]
-=== Authentication and authorization
+//[id="ocp-release-notes-auth_{context}"]
+//=== Authentication and authorization
 
-[id="ocp-release-notes-documentation_{context}"]
-=== Documentation
+//[id="ocp-release-notes-documentation_{context}"]
+//=== Documentation
 
 [id="ocp-release-notes-edge-computing_{context}"]
 === Edge computing
@@ -1008,8 +1008,8 @@ This new feature enhances TLS certificate rotations in {product-title}, ensuring
 
 With this update, the etcd product documentation is updated to include additional requirements for reducing {product-title} cluster latency. This update clarifies the prerequisites and setup procedures for using etcd, resulting in an improved user experience. As a result, this feature introduces support for Transport Layer Security (TLS) 1.3 in etcd, which enhances security and performance for data transmission, and enables etcd to comply with the latest security standards, reducing potential vulnerabilities. The improved encryption ensures more secure communication between etcd and its clients. For more information, see xref:../etcd/etcd-practices.adoc#recommended-cluster-latency-etcd_etcd-practices[Cluster latency requirements for etcd].
 
-[id="ocp-release-notes-security_{context}"]
-=== Security
+//[id="ocp-release-notes-security_{context}"]
+//=== Security
 
 [id="ocp-release-notes-storage_{context}"]
 === Storage
@@ -1365,14 +1365,14 @@ This prevents users from discovering certain problems only after the cache is po
 |====
 
 
-[id="ocp-hardware-an-driver-dep-rem_{context}"]
-=== Specialized hardware and driver enablement deprecated and removed features
+//[id="ocp-hardware-an-driver-dep-rem_{context}"]
+//=== Specialized hardware and driver enablement deprecated and removed features
 
-.Specialized hardware and driver enablement deprecated and removed tracker
-[cols="4,1,1,1",options="header"]
-|====
-|Feature |4.18 |4.19 |4.20
-|====
+//.Specialized hardware and driver enablement deprecated and removed tracker
+//[cols="4,1,1,1",options="header"]
+//|====
+//|Feature |4.18 |4.19 |4.20
+//|====
 
 
 === Storage deprecated and removed features
@@ -1389,14 +1389,14 @@ This prevents users from discovering certain problems only after the cache is po
 |====
 
 
-[id="ocp-clusters-dep-rem_{context}"]
-=== Updating clusters deprecated and removed features
+//[id="ocp-clusters-dep-rem_{context}"]
+//=== Updating clusters deprecated and removed features
 
-.Updating clusters deprecated and removed tracker
-[cols="4,1,1,1",options="header"]
-|====
-|Feature |4.18 |4.19 |4.20
-|====
+//.Updating clusters deprecated and removed tracker
+//[cols="4,1,1,1",options="header"]
+//|====
+//|Feature |4.18 |4.19 |4.20
+//|====
 
 
 [id="ocp-release-note-web-console-dep-rem_{context}"]
@@ -1517,8 +1517,8 @@ With this release, kubelet no longer reports resources for terminated pods, whic
 //Telco Edge / ZTP
 
 
-[id="ocp-release-note-api-auth-bug-fixes_{context}"]
-=== API Server and Authentication
+//[id="ocp-release-note-api-auth-bug-fixes_{context}"]
+//=== API Server and Authentication
 
 
 [id="ocp-release-note-bare-metal-hardware-bug-fixes_{context}"]
@@ -1659,12 +1659,8 @@ As a result, the controller handles errors during migration better.
 
 * Before this update, when you created a cluster autoscaler object with the Cluster Autoscaler Operator enabled in the cluster, two `cluster-autoscaler-default` pods in the `openshift-machine-api` were sometimes created at the same time and one of the pods was immediately killed. With this release, only one pod is created. (link:https://issues.redhat.com/browse/OCPBUGS-57041[OCPBUGS-57041])
 
-[id="ocp-release-note-cluster-override-admin-operator-bug-fixes_{context}"]
-=== Cluster Resource Override Admission Operator
-
-
-
-
+//[id="ocp-release-note-cluster-override-admin-operator-bug-fixes_{context}"]
+//=== Cluster Resource Override Admission Operator
 
 [id="ocp-release-note-cluster-version-operator-bug-fixes_{context}"]
 === Cluster Version Operator
@@ -1702,13 +1698,8 @@ As a result, the controller handles errors during migration better.
 
 * Before this update, the catalogd and Operator Controller components did not display the correct version and commit information in the {oc-first}. With this update, the correct commit and version information is displayed. (link:https://issues.redhat.com/browse/OCPBUGS-23055[OCPBUGS-23055])
 
-[id="ocp-release-note-image-streams-bug-fixes_{context}"]
-=== ImageStreams
-
-
-
-
-
+//[id="ocp-release-note-image-streams-bug-fixes_{context}"]
+//=== ImageStreams
 
 [id="ocp-release-note-installer-bug-fixes_{context}"]
 === Installer
@@ -1717,7 +1708,7 @@ As a result, the controller handles errors during migration better.
 
 * Before this update, when you installed a cluster on {azure-short} Stack Hub with a user-provisioned infrastructure, the API and API-int load balancers could fail to be created. As a consequence, the installation failed. With this release, the user-provisioned infrastructure templates is updated so that the load balancers are created. As a result, installation is successful. (link:https://issues.redhat.com/browse/OCPBUGS-60545[OCPBUGS-60545])
 
-* Before this update, when you installed a cluster on {gcp-short}, the installation program read and processed the `install-config.yaml` file even when an unrecoverable error was reported about not finding a matching public DNS zone. This error was due to an invalid `baseDomain` parameter. As a consequence, cluster administrators recreated the `install-config.yaml` file unnecessarily. With this release, when the installation program reports this error the installation progam does not read and process the `install-config.yaml` file. (link:https://issues.redhat.com/browse/OCPBUGS-59430[OCPBUGS-59430]) 
+* Before this update, when you installed a cluster on {gcp-short}, the installation program read and processed the `install-config.yaml` file even when an unrecoverable error was reported about not finding a matching public DNS zone. This error was due to an invalid `baseDomain` parameter. As a consequence, cluster administrators recreated the `install-config.yaml` file unnecessarily. With this release, when the installation program reports this error the installation progam does not read and process the `install-config.yaml` file. (link:https://issues.redhat.com/browse/OCPBUGS-59430[OCPBUGS-59430])
 
 * Before this update, {ibm-cloud-title} was omitted from the list of platforms that supported {sno} installation in the validation code. As a consequence, users could not install a single-node configuration on {ibm-cloud-title} because of a validation error. With this release, {ibm-cloud-title} support for single-node installations is enabled. As a result, users can complete single-node installations on {ibm-cloud-title}. (link:https://issues.redhat.com/browse/OCPBUGS-59220[OCPBUGS-59220])
 
@@ -2009,27 +2000,18 @@ With this release, the warning message no longer appears in the `metrics-server`
 
 * Before this update, the catalog Operator scheduled catalog snapshots for every 5 minutes. On clusters with many namespaces and subscriptions, snapshots failed and cascaded across catalog sources. As a result, the spikes in CPU loads effectively blocked installing and updating Operators. With this update, catalog snapshots are scheduled for every 30 minutes to allow enough time for the snapshotes to resolve. (link:https://issues.redhat.com/browse/OCPBUGS-43966[OCPBUGS-43966])
 
-[id="ocp-release-note-pao-bug-fixes_{context}"]
-=== Performance Addon Operator
+//[id="ocp-release-note-pao-bug-fixes_{context}"]
+//=== Performance Addon Operator
 
-
-
-
-
-
-[id="ocp-release-note-samples-operator-bug-fixes_{context}"]
-=== Samples Operator
+//[id="ocp-release-note-samples-operator-bug-fixes_{context}"]
+//=== Samples Operator
 
 
 [id="ocp-release-note-service-catalog-bug-fixes_{context}"]
 === Service Catalog
 
 * Before this update, setting an invalid certificate secret name in the service annotation `service.beta.openshift.io/serving-cert-secret-name` would cause the service Certificate Authority (CA) Operator to hot loop. With this release, the Operator stops retrying to create the secret after 10 tries. The number of retries cannot be changed. (link:https://issues.redhat.com/browse/OCPBUGS-61966[OCPBUGS-61966])
 
-
-
-
-
 [id="ocp-release-note-storage-bug-fixes_{context}"]
 === Storage
 
@@ -2038,11 +2020,8 @@ With this release, the warning message no longer appears in the `metrics-server`
 * Before this update, a race condition would sometimes cause an intermittent failure, or _flake_, when a Persistent Volume Claim (PVC) was resized too quickly after being created. This resulted in an error where the system would incorrectly report that the bound Persistent Volume (PV) could not be found. With this release, the timing issue was fixed, so resizing a PVC right after its creation works. (link:https://issues.redhat.com/browse/OCPBUGS-61546[OCPBUGS-61546])
 
 
-[id="ocp-release-note-rhcos-bug-fixes_{context}"]
-=== {op-system-first}
-
-
-
+//[id="ocp-release-note-rhcos-bug-fixes_{context}"]
+//=== {op-system-first}
 
 [id="ocp-release-technology-preview-tables_{context}"]
 == Technology Preview features status
@@ -2655,14 +2634,14 @@ In the following tables, features are marked with the following statuses:
 |====
 
 
-[id="ocp-release-notes-special-hardware-tech-preview_{context}"]
-=== Specialized hardware and driver enablement Technology Preview features
+//[id="ocp-release-notes-special-hardware-tech-preview_{context}"]
+//=== Specialized hardware and driver enablement Technology Preview features
 
-.Specialized hardware and driver enablement Technology Preview tracker
-[cols="4,1,1,1",options="header"]
-|====
-|Feature |4.18 |4.19 |4.20
-|====
+//.Specialized hardware and driver enablement Technology Preview tracker
+//[cols="4,1,1,1",options="header"]
+//|====
+//|Feature |4.18 |4.19 |4.20
+//|====
 
 
 [id="ocp-release-notes-storage-tech-preview_{context}"]
@@ -2865,11 +2844,11 @@ For any {product-title} release, always review the instructions on xref:../updat
 
 //Update with relevant advisory information
 [id="ocp-4-20-0-ga_{context}"]
-=== RHSA-202X:XXXXX - {product-title} {product-version}.0 image release, bug fix, and security update advisory
+=== RHSA-2025:9562 - {product-title} {product-version}.0 image release, bug fix, and security update advisory
 
-Issued: DD MMM YYYY
+Issued: 21 Oct 2025
 
-{product-title} release {product-version}.0, which includes security updates, 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-202X:XXXXX[RHSA-202X:XXXXX] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHEA-202X:XXXX[RHEA-202X:XXXX] advisory.
+{product-title} release {product-version}.0, which includes security updates, 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:9562[RHSA-2025:9562] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHEA-2025:4782[RHEA-2025:4782] advisory.
 
 Space precluded documenting all of the container images for this release in the advisory.
 
