gnelson/ocp-docs-suggestions-1k-pr huggingface dataset:
Original: * This release introduces the cluster interaction feature as technology preview feature. Use the cluster interaction feature to enhance the knowledge available to the large language model (LLM) with information about an {ocp-product-title} cluster. Providing cluster-specific information, such as the namespaces or pods that the cluster contains, enables the LLM to generate responses unique to the cluster.
Revised: * This release introduces the cluster interaction feature as a Technology Preview feature. Use the cluster interaction feature to enhance the knowledge available to the large language model (LLM) with information about an {ocp-product-title} cluster. Providing cluster-specific information, such as the namespaces or pods that the cluster contains, enables the LLM to generate responses unique to the cluster.
Original: You can configure the default timeouts for an existing route when you
have services in need of a low timeout, which is required for Service Level
Availability (SLA) purposes, or a high timeout, for cases with a slow
back end.
Revised: If you configured a user-managed load balancer for your network, ensure that the timeout value for the user-managed load balancer is higher than the timeout value for the route service. This configuration prevents congestion in load balancing scenarios.
Original: You can configure the default timeouts for an existing route when you
have services in need of a low timeout, which is required for Service Level
Availability (SLA) purposes, or a high timeout, for cases with a slow
back end.
Revised: If you configured a user-managed external load balancer in front of your {product-title} cluster, ensure that the timeout value for the user-managed external load balancer is higher than the timeout value for the route. This configuration prevents network congestion issues over the network that your cluster uses.
Original: {product-title} delivers an enterprise-ready distribution of the Red Hat-led open source community project {microshift-first}. {microshift-short} is a lightweight Kubernetes orchestration solution built from the edge capabilities of {OCP}, along with an edge-optimized operating system built from {op-system-first}.
Revised: {product-title} delivers an enterprise-ready distribution of the Red{nbsp}Hat-led open source community project {microshift-first} with {op-system-first} and {ansible}.
Original: With this release, {product-title} routes can be configured with third-party certificate management solutions, utilising the `.spec.tls.externalCertificate` field in the route API. This allows you to reference externally managed TLS certificates through secrets, streamlining the process by eliminating manual certificate management. By using externally managed certificates, you reduce errors, ensure a smoother certificate update process, and enable the OpenShift router to promptly serve renewed certificates. For more information, see xref:../../networking/index#nw-ingress-route-secret-load-external-cert_secured-routes[Creating a route with externally managed certificate].
Revised: With this release, {product-title} routes can be configured with third-party certificate management solutions, utilising the `.spec.tls.externalCertificate` field in the route API. This allows you to reference externally managed TLS certificates through secrets, streamlining the process by eliminating manual certificate management. By using externally managed certificates, you reduce errors, ensure a smoother certificate update process, and enable the OpenShift router to promptly serve renewed certificates. For more information, see xref:../../networking/index.adoc#nw-ingress-route-secret-load-external-cert_secured-routes[Creating a route with externally managed certificate].
Original: With this release, {product-title} routes can be configured with third-party certificate management solutions, utilising the `.spec.tls.externalCertificate` field in the route API. This allows you to reference externally managed TLS certificates through secrets, streamlining the process by eliminating manual certificate management. By using externally managed certificates, you reduce errors, ensure a smoother certificate update process, and enable the OpenShift router to promptly serve renewed certificates. For more information, see xref:../../networking/index.adoc#nw-ingress-route-secret-load-external-cert_secured-routes[Creating a route with externally managed certificate].
Revised: With this release, {product-title} routes can be configured with third-party certificate management solutions, utilising the `.spec.tls.externalCertificate` field in the route API. This allows you to reference externally managed TLS certificates through secrets, streamlining the process by eliminating manual certificate management. By using externally managed certificates, you reduce errors, ensure a smoother certificate update process, and enable the OpenShift router to promptly serve renewed certificates. For more information, see xref:../networking/routes/secured-routes.adoc#nw-ingress-route-secret-load-external-cert_secured-routes[Creating a route with externally managed certificate].
Original: Starting with {product-title} 4.19, the perspectives in the web console have unified to simplify navigation, reduce context switching, streamline tasks, and provide users with a more cohesive {product-title} experiance.
Revised: Starting with {product-title} 4.19, the perspectives in the web console have unified to simplify navigation, reduce context switching, streamline tasks, and provide users with a more cohesive {product-title} experience.
Original: [id="ocp-administrator-perspective_{context}"]
==== Administrator perspective
[id="ocp-developer-perspective_{context}"]
==== Developer Perspective
Revised: With this unified design, there is no longer a *Developer* perspective in the default view; however, _all_ {product-title} web console features are discoverable to all users. If you are not the cluster owner, you might need to request permission for certain features from the cluster owner. You can still enable the *Developer* perspective.
Original: [id="ocp-administrator-perspective_{context}"]
==== Administrator perspective
[id="ocp-developer-perspective_{context}"]
==== Developer Perspective
Revised: With this unified design, there is no longer a *Developer* perspective in the default view; however, _all_ {product-title} web console features are discoverable to all users. If you are not the cluster owner, you might need to request permission for certain features from the cluster owner. The *Developer* perspective can still be manually enabled if you prefer.
Original: cpuModels: <1>
minCPUModel: "<minimum_cpu_model>" <2>
<1> Replace the example values in the `cpuModels` array with obsolete CPU models. Any value that you specify is added to a predefined list of obsolete CPU models. The predefined list is not visible in the CR.
<2> Replace this value with the minimum CPU model that you want to use for basic CPU features. If you do not specify a value, `Penryn` is used by default.
Revised: <1> Specifies obsolete CPU models to be added to a predefined list of obsolete CPU models. The predefined list is not visible in the CR.
Original: * **xref:../applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc#odc-creating-applications-using-developer-perspective[Work with applications]**:
Use xref:../web_console/web-console-overview.adoc#about-developer-perspective_web-console-overview[the *Developer* perspective] in the {product-title} web console to
xref:../applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc#odc-creating-applications-using-developer-perspective[create and deploy applications].
Revised: // Commenting out until updates to module are made for unified perspective.
Original: You can still enable the *Developer* perspective. The *Getting Started* pane in the web console provides resources such as, a tour of the console, information on setting up your cluster, a quick start for enabling the *Developer* perspective, and links to explore new features and capabilities.
Revised: You can still enable the *Developer* perspective. On the *Getting Started* pane in the web console, you can  take a tour of the console, find information on setting up your cluster, view a quick start for enabling the *Developer* perspective, and follow links to explore new features and capabilities.
Original: * When a pod uses the CNI plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might be unexpectedly deleted. As a result, when the pod's DHCP lease expires, the DHCP proxy enters a loop when trying to re-create a new lease, leading to the node becoming unresponsive. There is currently no known workaround. (link:https://issues.redhat.com/browse/OCPBUGS-55354[OCPBUGS-55354])
Revised: * When a pod uses the Container Network Interface (CNI) plugin for DHCP address assignment, in conjunction with other CNI plugins, the pod's network interface might be unexpectedly deleted. As a result, when the pod's DHCP lease expires, the DHCP proxy enters a loop when trying to re-create a new lease, leading to the node becoming unresponsive. There is currently no known workaround. (link:https://issues.redhat.com/browse/OCPBUGS-55354[OCPBUGS-55354])
Original: * Previously, the sample operator watched all of the 'ClusterOperators' on any cluster operator where changes to the cluster triggered the syncloop to run. The resulted in excessive and unnecessary syncloop triggers negatively impacting overall performance. With this release, the 'ClusterOperator' watch was modified to filter for changes only to the 'openshift-samples' 'ClusterOperator', reducing unnecessary syncloops leading to improved performance. (link:https://issues.redhat.com/browse/OCPBUGS-55781[OCPBUGS-55781])
Revised: * Previously, the sample Operator detected all of the `ClusterOperators` on any cluster Operator where changes to the cluster triggered the sync loop to run. This change resulted in excessive and unnecessary sync loop triggers that negatively impacted the overall performance. With this release, the `ClusterOperator` watch was modified to filter for changes only to the `openshift-samples` cluster Operator`, reducing unnecessary sync loops and improving performance. (link:https://issues.redhat.com/browse/OCPBUGS-55781[OCPBUGS-55781])
Original: * Currently, when adding a node in a disconnected environment, private registry images are inaccessible for the 'oc adm node-image' command, causing node addition failure due to image pull issues. This error only occurs if the cluster is initially installed with an installer binary downloaded from mirror.openshift.com. With this release, a fix has been implemented enabling successful image pull and node creation in disconnected environments. (link:https://issues.redhat.com/browse/OCPBUGS-55449[OCPBUGS-55449])
Revised: * Currently, when adding a node in a disconnected environment, private registry images are inaccessible for the `oc adm node-image` command, causing node addition failure due to image pull issues. This error only occurs if the cluster is initially installed with an installation program binary downloaded from mirror.openshift.com. With this release, a fix has been implemented resulting in a successful image pull and node creation in disconnected environments. (link:https://issues.redhat.com/browse/OCPBUGS-55449[OCPBUGS-55449])
Original: * Currently, there is an issue in the image reference digest calculation leading to a failed container creation based on the schemaVersion 1 image. This prevents new deployment creations. With this release, the image digest calculation has been fixed and new operators can be installed. (link:https://issues.redhat.com/browse/OCPBUGS-55435[OCPBUGS-55435])
Revised: * Previously, there was an issue in the image reference digest calculation that led to a failed container creation based on the `schemaVersion 1` image. This prevented new deployment creations. With this release, the image digest calculation is fixed and new Operators can be installed. (link:https://issues.redhat.com/browse/OCPBUGS-55435[OCPBUGS-55435])
Original: * Previously, Azure spot machines that evicted before their node became ready, could get stuck in the 'provisioned' state. With this release, Azure spot instances now use a delete eviction policy, ensuring the machines correctly transition to the 'failed' state upon preemption. (link:https://issues.redhat.com/browse/OCPBUGS-55373[OCPBUGS-55373])
Revised: * Previously, {azure-first} noted machines that were evicted before their node was ready,  and the nodes could get stuck in the 'provisioned' state. With this release, Azure instances use a delete eviction policy, ensuring the machines correctly transition to the `failed` state upon preemption. (link:https://issues.redhat.com/browse/OCPBUGS-55373[OCPBUGS-55373])
Original: * Previously, the `oc-mirror` plugin returned an exit status of `0` (success) even when mirroring errors occurred in automated workflows. As a result, customers could not rely on the exit status in the automated workflows. With this release, the `oc mirror` returns a non-zero (failure) exit status when there are errors. (link:https://issues.redhat.com/browse/OCPBUGS-54626[OCPBUGS-54626])
Revised: * Previously, the `oc-mirror` plugin returned an exit status of `0` (success) even when mirroring errors occurred in automated workflows. As a result, customers could not rely on the exit status in the automated workflows. With this release, the `oc mirror` returns a null (failure) exit status when there are errors. (link:https://issues.redhat.com/browse/OCPBUGS-54626[OCPBUGS-54626])
Original: * Previously, the 4.18 machine-config operators were unaware that the package-based Red Hat Enterprise Linux (RHEL) support was removed in 4.19. With this release,these operators will block updates to 4.19 on clusters with packaged-based RHEL nodes, ensuring compatibility. (link:https://issues.redhat.com/browse/OCPBUGS-53427[OCPBUGS-53427])
Revised: * Previously, the 4.18 Machine Config Operators (MCO) were unaware that the package-based Red Hat Enterprise Linux (RHEL) support was removed in 4.19. With this release, these Operators block updates to 4.19 on clusters with packaged-based RHEL nodes, ensuring compatibility. (link:https://issues.redhat.com/browse/OCPBUGS-53427[OCPBUGS-53427])
Original: {product-title} release {product-version}.12 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:4712[RHSA-2025:4712] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:4714[RHBA-2025:4714] advisory.
Revised: {product-title} release {product-version}.13 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:4712[RHSA-2025:4712] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:4714[RHBA-2025:4714] advisory.
Original: * Previously, unsorted image stream names in the `Progressing` condition were causing unnecessary updates. This led to excessive user updates and potential performance degradation. With this release, the failing image imports are sorted within the `activeImageStreams` function improving sample operator efficiency, reducing unnecessary updates, and enhancing overall performance. (link:https://issues.redhat.com/browse/OCPBUGS-55783[OCPBUGS-55783])
Revised: * Previously, unsorted image stream names in the `Progressing` condition caused unnecessary updates. This led to excessive user updates and potential performance degradation. With this release, the failing image imports are sorted within the `activeImageStreams` function improving sample operator efficiency, reducing unnecessary updates, and enhancing overall performance. (link:https://issues.redhat.com/browse/OCPBUGS-55783[OCPBUGS-55783])
Original: * Previously, unsorted image stream names in the `Progressing` condition caused unnecessary updates. This led to excessive user updates and potential performance degradation. With this release, the failing image imports are sorted within the `activeImageStreams` function improving sample operator efficiency, reducing unnecessary updates, and enhancing overall performance. (link:https://issues.redhat.com/browse/OCPBUGS-55783[OCPBUGS-55783])
Revised: * Previously, unsorted image stream names in the `Progressing` condition caused unnecessary updates. This led to excessive user updates and potential performance degradation. With this release, the failing image imports are sorted within the `activeImageStreams` function. This change improves Cluster Samples Operator efficiency, reduces unnecessary updates, and enhances overall performance. (link:https://issues.redhat.com/browse/OCPBUGS-55783[OCPBUGS-55783])
Original: * Previously, an operator updated the 'Progressing' condition's `lastTransitionTime` even when the condition's status did not actually change. This led to potential installation errors and perceived instability for end users. With this release, the operator is prevented from updating the `lastTransitionTime` unless there is a status change, enhancing operator stability, minimizing installer errors, and ensuring a smoother user experience. (link:https://issues.redhat.com/browse/OCPBUGS-55782[OCPBUGS-55782])
Revised: * Previously, an Operator updated the `Progressing` condition's `lastTransitionTime` value even when the condition's status did not actually change. This led to potential installation errors and perceived instability for end users. With this release, the Operator is prevented from updating the `lastTransitionTime` value unless there is a status change. This update enhances Operator stability, minimizes installation errors, and ensures a smoother user experience. (link:https://issues.redhat.com/browse/OCPBUGS-55782[OCPBUGS-55782])
Original: * Previously, the sample Operator detected all of the 'ClusterOperators' on any cluster Operator where changes to the cluster triggered the sync loop to run. This change resulted in excessive and unnecessary sync loop triggers that negatively impacted the overall performance. With this release, the 'ClusterOperator' watch was modified to filter for changes only to the 'openshift-samples' 'cluster Operator', reducing unnecessary sync loops and improving performance. (link:https://issues.redhat.com/browse/OCPBUGS-55781[OCPBUGS-55781])
Revised: * Previously, the Cluster Samples Operator watched all cluster Operators in the cluster, which triggered the Cluster Samples Operator sync loop to run unnecessarily. This behavior negatively impacted overall performance. With this release, the Cluster Samples Operator only watches specific cluster Operators. (link:https://issues.redhat.com/browse/OCPBUGS-55781[OCPBUGS-55781])
Original: * Previously, when adding a node in a disconnected environment, private registry images are inaccessible for the `oc adm node-image` command, causing node addition failure due to image pull issues. This error only occurs if the cluster is initially installed with an installation program binary downloaded from mirror.openshift.com. With this release, a fix has been implemented resulting in a successful image pull and node creation in disconnected environments. (link:https://issues.redhat.com/browse/OCPBUGS-55449[OCPBUGS-55449])
Revised: * Previously, when adding a node in a disconnected environment, private registry images were inaccessible for the `oc adm node-image` command. As a result, issues with pulling images prevented adding a node. This error only occurs if the cluster is initially installed with an installation program binary downloaded from `\mirror.openshift.com`. The issue is resolved in this release. (link:https://issues.redhat.com/browse/OCPBUGS-55449[OCPBUGS-55449])
Original: * Previously, there was an issue in the image reference digest calculation that led to a failed container creation based on the schemaVersion 1 image. This prevented new deployment creations. With this release, the image digest calculation is fixed and the new Operators can be installed. (link:https://issues.redhat.com/browse/OCPBUGS-55435[OCPBUGS-55435])
Revised: * Previously, there was an issue in the image reference digest calculation that led to a failed container creation based on the Schema version 1 image. This prevented new deployment creations. With this release, the image digest calculation is fixed and the new Operators can be installed. (link:https://issues.redhat.com/browse/OCPBUGS-55435[OCPBUGS-55435])
Original: * Previously, Azure spot machines that evicted before their node became ready, could get stuck in the 'provisioned' state. With this release, Azure spot instances now use a delete eviction policy, ensuring the machines correctly transition to the 'failed' state upon preemption. (link:https://issues.redhat.com/browse/OCPBUGS-55373[OCPBUGS-55373])
Revised: * Previously, {azure-first} Spot Virtual Machines (VMs) that were evicted before their node became ready could get stuck in the `provisioned` state. With this release, {azure-short} Spot VMs now use a delete eviction policy, ensuring that the VMs correctly transition to the `failed` state if they are preempted. (link:https://issues.redhat.com/browse/OCPBUGS-55373[OCPBUGS-55373])
Original: * Previously, the `oc-mirror` plugin returned an exit status of `0` (success) even when mirroring errors occurred in automated workflows. As a result, customers could not rely on the exit status in the automated workflows. With this release, the `oc mirror` returns a null (failure) exit status when there are errors. (link:https://issues.redhat.com/browse/OCPBUGS-54626[OCPBUGS-54626])
Revised: * Previously, the `oc-mirror` plugin returned an exit status of `0`, indicating success, even when mirroring errors occurred in automated workflows. As a result, customers could not rely on the exit status in the automated workflows. With this release, the `oc mirror` plugin returns a null exit status, indicating failure, when there are errors. (link:https://issues.redhat.com/browse/OCPBUGS-54626[OCPBUGS-54626])
Original: * Previously, an image pull secret generated for the internal Image Registry would not be regenerated until after the embedded credentials had expired This resulted in a small period of time in which the image pull secrets were invalid. With this release, the image pull secrets are refreshed before the embedded credentials have expired. (link:https://issues.redhat.com/browse/OCPBUGS-54304[OCPBUGS-54304])
Revised: * Previously, an image pull secret generated for the internal image registry was not regenerated until after the embedded credentials expired. This resulted in a small period of time during which the image pull secrets were invalid. With this release, the image pull secrets are refreshed before the embedded credentials expire. (link:https://issues.redhat.com/browse/OCPBUGS-54304[OCPBUGS-54304])
Original: * Previously, the 4.18 Machine Config Operators (MCO) were unaware that the package-based Red Hat Enterprise Linux (RHEL) support was removed in 4.19. With this release,these Operators will block updates to 4.19 on clusters with packaged-based RHEL nodes, ensuring compatibility. (link:https://issues.redhat.com/browse/OCPBUGS-53427[OCPBUGS-53427])
Revised: * Previously, the Machine Config Operator (MCO) in {product-title} 4.18 was not updated to reflect that package-based {op-system-base-full} support was removed in {product-title} 4.19. With this release, this Operator ensures compatibility by blocking updates to {product-title} 4.19 on clusters with packaged-based {op-system-base} nodes. (link:https://issues.redhat.com/browse/OCPBUGS-53427[OCPBUGS-53427])