gnelson/ocp-docs-suggestions-1k-pr huggingface dataset:
Original: * Previously, the installer failed when Amazon Web Service (AWS) credentials were not found and the survey was attempting AWS regions preventing users from creating the install-config. With this release, the installer no longer fails when AWS credentials are not set, allow users to input them during the survey. (link:https://issues.redhat.com/browse/OCPBUGS-57394[OCPBUGS-57394])
Revised: * Previously, the installer failed when AWS credentials were not found and the survey was attempting AWS regions preventing users from creating the install-config. With this release, the installer no longer fails when AWS credentials are not set, allow users to input them during the survey. (link:https://issues.redhat.com/browse/OCPBUGS-57394[OCPBUGS-57394])
Original: * Previously, cloning the Red Hat OpenShift Console Persistent Volume Claim (PVC) resulted in an error due to an unsupported unit *B* for storage size. Because of this, users encountered errors when cloning the Red Hat OpenShift console PVC due to incorrect parsing of the storage size unit. With this release, support for *B* as unit of storage size has been removed from the Red Hat OpenShift console PVC. (link:https://issues.redhat.com/browse/OCPBUGS-57391[OCPBUGS-57391])
Revised: * Previously, cloning a persistent volume claim (PVC) in the web console resulted in an error due to an unsupported unit *B* for storage size. Because of this, users encountered errors when cloning a PVC due to incorrect parsing of the storage size unit. With this release, support for *B* as unit of storage size has been removed. (link:https://issues.redhat.com/browse/OCPBUGS-57391[OCPBUGS-57391])
Original: * Previously, `OLMv1` was used to install Operators with the `olm.maxOpenShiftVersion` set to  `4.19`.  Due to an issue with the `OLMv1` parsing logic for floating-point formatted `olm.maxOpenShiftVersion`values, the system failed to prevent upgrades to Red Hat OpenShift 4.20. With this release, the parsing logic for  `olm.maxOpenShiftVersion` has been corrected preventing upgrades to Red Hat OpenShift 4.20 when Operators with `olm.maxOpenShiftVersion:4.19` are installed. (link:https://issues.redhat.com/browse/OCPBUGS-56852[OCPBUGS-56852])
Revised: * Previously, `OLMv1` was used to install Operators with the `olm.maxOpenShiftVersion` set to  `4.19`.  Due to an issue with the `OLMv1` parsing logic for floating-point formatted `olm.maxOpenShiftVersion` values, the system failed to prevent upgrades to {product-title} 4.20. With this release, the parsing logic for  `olm.maxOpenShiftVersion` has been corrected, preventing upgrades to {product-title} 4.20 when Operators with `olm.maxOpenShiftVersion:4.19` are installed. (link:https://issues.redhat.com/browse/OCPBUGS-56852[OCPBUGS-56852])
Original: * Previously, the installer failed when AWS credentials were not found and the survey was attempting AWS regions preventing users from creating the install-config. With this release, the installer no longer fails when AWS credentials are not set, allow users to input them during the survey. (link:https://issues.redhat.com/browse/OCPBUGS-57394[OCPBUGS-57394])
Revised: * Previously, the installer failed when AWS credentials were not found and the survey was attempting AWS regions preventing users from creating the `install-config` file. With this release, the installer no longer fails when AWS credentials are not set, allowing users to input them during the survey. (link:https://issues.redhat.com/browse/OCPBUGS-57394[OCPBUGS-57394])
Original: * The `oc-mirror v2` was not using the correct filtered catalog during its operations, which led to errors such as including more operators than specified in the configuration, and trying to connect to the catalog registry during disk-to-mirror workflows even in air-gapped environments. With this release, the correct filtered catalog is used. (link:https://issues.redhat.com/browse/OCPBUGS-57784[OCPBUGS-57784])
Revised: * Previously, the `oc-mirror v2` command was not using the correct filtered catalog during its operations, which led to errors such as including more operators than specified in the configuration, and trying to connect to the catalog registry during disk-to-mirror workflows even in air-gapped environments. With this release, the correct filtered catalog is used. (link:https://issues.redhat.com/browse/OCPBUGS-57784[OCPBUGS-57784])
Original: * Previously, a validation issue within `oc-mirror` causes the command to reject the `file://.` reference. Users attempting to use `file://.` for a content path received an error message stating `content filepath is tainted`. With this release, `oc-mirror` properly validates the '.' directory reference. (link:https://issues.redhat.com/browse/OCPBUGS-57786[OCPBUGS-57786])
Revised: * Previously, a validation issue within the `oc-mirror` plugin caused the command to reject the `file://.` reference. Users attempting to use `file://.` for a content path received an error message stating `content filepath is tainted`. With this release, the `oc-mirror` plugin properly validates the '.' directory reference. (link:https://issues.redhat.com/browse/OCPBUGS-57786[OCPBUGS-57786])
Original: * Previously, if a user specified a custom boot image for Amazon Web Services (AWS) or the Google Cloud Platform (GCP), the Machine Config Operator (MCO) would overwrite it with the default boot image during installation. With this release, a manifest generation was added for MCO configuration which disables the default boot image during installation if a custom image is specified. (link:https://issues.redhat.com/browse/OCPBUGS-57796[OCPBUGS-57796])
Revised: * Previously, if a user specified a custom boot image for {aws-first} or the {gcp-first}, the Machine Config Operator (MCO) would overwrite it with the default boot image during installation. With this release, a manifest generation was added for MCO configuration which disables the default boot image during installation if a custom image is specified. (link:https://issues.redhat.com/browse/OCPBUGS-57796[OCPBUGS-57796])
Original: * Previously, the installation program checked only the first compute machine pool entry in the install configuration to determine whether to disable the Machine Config Operator (MCO) boot image management feature. If multiple compute pools were specified (Amazon Web Service (AWS) edge nodes are the only supported scenario), but another compute machine pool had a custom Amazon Machine Image (AMI), the installation program would not disable the MCO boot image management and the custom AMI would be overwritten by the MCO. With this release, the installation program checks all compute machine pool entries and if a custom image is found, the MCO boot image management is disabled. (link:https://issues.redhat.com/browse/OCPBUGS-58060[OCPBUGS-58060])
Revised: * Previously, the installation program checked only the first compute machine pool entry in the install configuration to determine whether to disable the Machine Config Operator (MCO) boot image management feature. If multiple compute pools were specified ({aws-first} edge nodes are the only supported scenario), but another compute machine pool had a custom Amazon Machine Image (AMI), the installation program would not disable the MCO boot image management and the custom AMI would be overwritten by the MCO. With this release, the installation program checks all compute machine pool entries and if a custom image is found, the MCO boot image management is disabled. (link:https://issues.redhat.com/browse/OCPBUGS-58060[OCPBUGS-58060])
Original: * Previously, cloning a persistent volume claim (PVC) in the web console resulted in an error due to an unsupported unit *B* for storage size. Because of this, users encountered errors when cloning the Red Hat OpenShift console PVC due to incorrect parsing of the storage size unit. With this release, support for *B* as unit of storage size has been removed from the Red Hat OpenShift console PVC. (link:https://issues.redhat.com/browse/OCPBUGS-57391[OCPBUGS-57391])
Revised: * Previously, cloning a persistent volume claim (PVC) in the web console resulted in an error due to an unsupported unit *B* for storage size. Because of this, users encountered errors when cloning the Red Hat OpenShift console PVC due to incorrect parsing of the storage size unit. With this release, support for *B* as unit of storage size has been removed from the Red{nbsp}Hat OpenShift console PVC. (link:https://issues.redhat.com/browse/OCPBUGS-57391[OCPBUGS-57391])
Original: * Previously, `OLMv1` was used to install Operators with the `olm.maxOpenShiftVersion` set to  `4.19`.  Due to an issue with the `OLMv1` parsing logic for floating-point formatted `olm.maxOpenShiftVersion`values, the system failed to prevent upgrades to {product-title}. With this release, the parsing logic for  `olm.maxOpenShiftVersion` has been corrected preventing upgrades to {product-title} when Operators with `olm.maxOpenShiftVersion:4.19` are installed. (link:https://issues.redhat.com/browse/OCPBUGS-56852[OCPBUGS-56852])
Revised: * Previously, {olmv1-first} was used to install Operators with the `olm.maxOpenShiftVersion` set to  `4.19`.  Due to an issue with the {olmv1} parsing logic for floating-point formatted `olm.maxOpenShiftVersion`values, the system failed to prevent upgrades to {product-title}. With this release, the parsing logic for  `olm.maxOpenShiftVersion` has been corrected preventing upgrades to {product-title} when Operators with `olm.maxOpenShiftVersion:4.19` are installed. (link:https://issues.redhat.com/browse/OCPBUGS-56852[OCPBUGS-56852])
Original: R-IOV related kernel arguments,xref:../../telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc#ztp-07-sriov-related-kernel-args-worker-yaml[07-sriov-related-kernel-args-worker.yaml],No,No
Revised: SR-IOV related kernel arguments,xref:../../telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc#ztp-07-sriov-related-kernel-args-worker-yaml[07-sriov-related-kernel-args-worker.yaml],No,No
Original: The following requirements in this topic apply to {product-title} on {GCP} clusters created using both the service account and Workload Identity Federation authentication type. For additional requirements that apply to the service account authentication type only, see _Service account authentication type procedure_. For additional requirements that apply to the Workload Identity Federation authentication type only, see _Workload Identity Federation authentication type procedure_.
Revised: The following requirements in this topic apply to {product-title} on {GCP} clusters created using both the Workload Identity Federation (WIF) and service account authentication types.
Original: The following requirements in this topic apply to {product-title} on {GCP} clusters created using both the service account and Workload Identity Federation authentication type. For additional requirements that apply to the service account authentication type only, see _Service account authentication type procedure_. For additional requirements that apply to the Workload Identity Federation authentication type only, see _Workload Identity Federation authentication type procedure_.
Revised: Red{nbsp}Hat recommends using WIF as the authentication type for installing and interacting with an {product-title} cluster deployed on GCP because WIF provides enhanced security.
Original: The Customer Cloud Subscription (CCS) model allows Red{nbsp}Hat to deploy and manage {product-title} into a customer's Google Cloud Platform (GCP) project. Red Hat requires several prerequisites to provide these services.
Revised: The Customer Cloud Subscription (CCS) model allows Red{nbsp}Hat to deploy and manage {product-title} into a customer's Google Cloud Platform (GCP) project. Red{nbsp}Hat requires several prerequisites to be completed before providing these services.
Original: If you update only the trusted CA for your cluster, the MCO updates the `/etc/pki/ca-trust/source/anchors/openshift-config-user-ca-bundle.crt` file and the Machine Config Controller (MCC) applies the trusted CA update to each node so that a node reboot is not required. Changing any other parameter in the `openshift-config-user-ca-bundle.crt` file, such as `noproxy`, results in the MCO rebooting each node in your cluster.
Revised: If you change any other parameter in the `openshift-config-user-ca-bundle.crt` file, such as `noproxy`, the MCO reboots each node in your cluster.
Original: . To verify that the Prometheus instance has added new targets and to also verify the alert, you can use a port-forward command to expose the Prometheus or Alertmanager user interfaces that have been deployed by the `Monitoringstack` instance.
Revised: . Verify that the Prometheus instance adds new targets. Verify that the alert is active by using a port-forward command to expose the Prometheus or Alertmanager user interface deployed by the `Monitoringstack` instance.
Original: . Verify that the Prometheus instance adds new targets and that the alert are firing. Use a port-forward command to expose the Prometheus or the Alertmanager user interface that has been deployed by the `Monitoringstack` instance.
Revised: . Verify that the Prometheus instance adds new targets and that the alert are firing as expected. To expose the Prometheus or the Alertmanager user interface that has been deployed by your `Monitoringstack` instance, use the port-forward command.
Original: * xref:../../storage/container_storage_interface/persistent-storage-csi-aws-efs.adoc#persistent-storage-csi-aws-efs[AWS Elastic File Service CSI Driver Operator].
Revised: * xref:../../storage/container_storage_interface/persistent-storage-csi-aws-efs.adoc#persistent-storage-csi-aws-efs[AWS Elastic File Service CSI Driver Operator]
Original: The suffixes for each byte quantity are case-sensitive. Be sure to use the correct case. Use the case-sensitive "M", such as used in "400M" to set the request at 400 megabytes. Use the case-sensitive "400Mi" to request 400 mebibytes. If you specify "400m" of ephemeral storage, the storage requests is only 0.4 bytes.
Revised: The suffixes for each byte quantity are case-sensitive. Be sure to use the correct case. Use the case-sensitive "M", such as used in "400M", to set the request at 400 megabytes. Use the case-sensitive "400Mi" to request 400 mebibytes. If you specify "400m" of ephemeral storage, the storage request is only 0.4 bytes.
Original: The recommended value is `true`.
|`metrics.disableHTTP2`
|If `true`, disables HTTP/2 for the metrics server as a mitigation for https://access.redhat.com/security/cve/cve-2023-44487[CVE-2023-44487]. The recommended value is `true`.
|`metrics.bindAddress`
|Determines the bind address for the metrics server. If unspecified, the default is `:8080`. To disable the metrics server, set to `0`. The recommended value is `0.0.0.0:8443`.
Revised: |If `true`, disables HTTP/2 for the webhook server, as a mitigation for link:https://access.redhat.com/security/cve/cve-2023-44487[CVE-2023-44487]. The default value is `true`.
Original: The recommended value is `true`.
|`metrics.disableHTTP2`
|If `true`, disables HTTP/2 for the metrics server as a mitigation for https://access.redhat.com/security/cve/cve-2023-44487[CVE-2023-44487]. The recommended value is `true`.
|`metrics.bindAddress`
|Determines the bind address for the metrics server. If unspecified, the default is `:8080`. To disable the metrics server, set to `0`. The recommended value is `0.0.0.0:8443`.
|`metrics.secureServing`
|Determines whether the metrics are served over HTTPS instead of HTTP. The recommended value is `true`.
|Determines the value of the `runAsUser` field of the worker container's security context. For more information, see link:https://kubernetes.io/docs/tasks/configure-pod-container/security-context/[SecurityContext]. The recommended value is `9443`.
|Determines the value of the `seLinuxOptions.type` field of the worker container's security context. For more information, see link:https://kubernetes.io/docs/tasks/configure-pod-container/security-context/[SecurityContext]. The recommended value is `spc_t`.
Revised: |Determines the value of the `seLinuxOptions.type` field of the worker container's security context. For more information, see link:https://kubernetes.io/docs/tasks/configure-pod-container/security-context/[SecurityContext]. The default value is `spc_t`.
Original: The recommended value is `true`.
|`metrics.disableHTTP2`
|If `true`, disables HTTP/2 for the metrics server as a mitigation for https://access.redhat.com/security/cve/cve-2023-44487[CVE-2023-44487]. The recommended value is `true`.
|`metrics.bindAddress`
|Determines the bind address for the metrics server. If unspecified, the default is `:8080`. To disable the metrics server, set to `0`. The recommended value is `0.0.0.0:8443`.
|`metrics.secureServing`
|Determines whether the metrics are served over HTTPS instead of HTTP. The recommended value is `true`.
|Determines the value of the `runAsUser` field of the worker container's security context. For more information, see link:https://kubernetes.io/docs/tasks/configure-pod-container/security-context/[SecurityContext]. The recommended value is `9443`.
|Determines the value of the `seLinuxOptions.type` field of the worker container's security context. For more information, see link:https://kubernetes.io/docs/tasks/configure-pod-container/security-context/[SecurityContext]. The recommended value is `spc_t`.
|`worker.setFirmwareClassPath`
|Sets the kernel's firmware search path into the `/sys/module/firmware_class/parameters/path` file on the node. The recommended value is `/var/lib/firmware` if you need to set that value through the worker app. Otherwise, unset.
Revised: |If set, the value of this field is written by the worker container into the /sys/module/firmware_class/parameters/path file on the node. For more information see link:https://openshift-kmm.netlify.app/documentation/firmwares/#setting-the-kernels-firmware-search-path[Setting the kernel's firmware search path]. The default value is `/var/lib/firmware`.
Original: * Previously, a bug was triggered when adding vCenter cloud credentials for the post installation of the {ai-full} because of an invalid ConfigMap object for the cloud provider configuration. As a result, a `missing vcenterplaceholder` error was displayed. With this release, the ConfigMap data is correct, and the error is not displayed. (link:https://issues.redhat.com/browse/OCPBUGS-57384[OCPBUGS-57384])
Revised: * Previously, when you added vCenter cloud credentials for the post installation of the {ai-full}, a bug was triggered because of an invalid `ConfigMap` object for the cloud provider configuration. As a result, a `missing vcenterplaceholder` error was displayed. With this release, the `ConfigMap` data is correct, and the error is not displayed. (link:https://issues.redhat.com/browse/OCPBUGS-57384[OCPBUGS-57384])
Original: * Previously, a network issue during an API call in a cluster caused a timeout in {olmv0-first}. As a result, Operator installations often failed because of timeout issues. With this release, the catalog cache refresh interval is updated to resolve timeout issues. As a result, the likelihood of Operator installation timeouts is reduced. (link:https://issues.redhat.com/browse/OCPBUGS-57352[OCPBUGS-57352])
Revised: * Previously, a network issue during an API call in a cluster caused a timeout in {olmv0-first}. As a consequence, Operator installations often failed because of timeout issues. With this release, the catalog cache refresh interval is updated to resolve timeout issues. As a result, the likelihood of Operator installation timeouts is reduced. (link:https://issues.redhat.com/browse/OCPBUGS-57352[OCPBUGS-57352])
Original: * Previously, ignoring the `AdditionalTrustBundlePolicy` in assisted-service's installation configuration caused users to incorrectly set the `AdditionalTrustBundlePolicy`, affecting Federal Information Processing Standard (FIPS) and other installation configuration overrides. With this release, the installation configuration includes an `AdditionalTrustBundlePolicy` field, ensuring overrides are applied correctly. Users can correctly set the `AdditionalTrustBundlePolicy` field, and ensure that FIPS and other installation configuration overrides function as intended. (link:https://issues.redhat.com/browse/OCPBUGS-57208[OCPBUGS-57208])
Revised: * Previously, the `AdditionalTrustBundlePolicy` setting in the assisted-service installation configuration led to Federal Information Processing Standard (FIPS) and other installation-configuration overrides. With this release, the installation configuration includes an `AdditionalTrustBundlePolicy` field, which you can set to ensure that FIPS and other installation-configuration overrides function as intended. (link:https://issues.redhat.com/browse/OCPBUGS-57208[OCPBUGS-57208])
Original: * Previously, the `Started` column was hidden because of reduced screen size. This caused the `VirtualizedTable` component to malfunction because of a missing sort function. As a result, the table sorting functionality was affected in the `PipelineRun` list pages. With this release, the table component handles missing sort functions correctly for reduced screen sizes. (link:https://issues.redhat.com/browse/OCPBUGS-57110[OCPBUGS-57110]) 
Revised: * Previously, the *Started* column was hidden when screen size was reduced. As a consequence, the `VirtualizedTable` component malfunctioned because of a missing sort function, and the table sorting functionality was affected on the *PipelineRun* list pages. With this release, the table component handles missing sort functions correctly for reduced screen sizes. (link:https://issues.redhat.com/browse/OCPBUGS-57110[OCPBUGS-57110])
Original: * Previously, users did not configure a default masthead logo when customizing the theme. This omission caused an inconsistency in the user interface. With this release, the masthead logo displays a default option for both light and dark themes, improving the interface consistency. (link:https://issues.redhat.com/browse/OCPBUGS-57054[OCPBUGS-57054])
Revised: * Previously, if you configured a masthead logo for a theme but used the default settings for the rest of the theme, the logo shown on the user interface was inconsistent. With this release, the masthead logo displays a default option for both light and dark themes, improving the interface consistency. (link:https://issues.redhat.com/browse/OCPBUGS-57054[OCPBUGS-57054])
Original: * Previously, the cluster installation failed because of an invalid security group configuration for  a Network Load Balancer (NLB). This failure prevented the traffic from both primary subnets for bootstrapping. With this release, the security group is updated to allow traffic from both primary subnets for bootstrapping, and the cluster installation does not fail because of security group restrictions on additional primary subnets. (link:https://issues.redhat.com/browse/OCPBUGS-57039[OCPBUGS-57039])
Revised: * Previously, the cluster installation failed because of an invalid security group configuration for a Network Load Balancer (NLB). This failure prevented the traffic from both primary subnets for bootstrapping. With this release, the security group allows traffic from both primary subnets for bootstrapping, and the cluster installation does not fail because of security group restrictions on additional primary subnets. (link:https://issues.redhat.com/browse/OCPBUGS-57039[OCPBUGS-57039])
Original: * Previously, users without project access saw an incomplete roles list because of improper API group access. As a result, users saw partial role information on the *Roles* page. With this release, users without project access cannot see an incomplete roles list on the *Roles* page. (link:https://issues.redhat.com/browse/OCPBUGS-56987[OCPBUGS-56987])
Revised: * Previously, users without project access saw an incomplete roles list on the *Roles* page because of improper API group access. With this release, users without project access cannot see an incomplete roles list on the *Roles* page. (link:https://issues.redhat.com/browse/OCPBUGS-56987[OCPBUGS-56987])