From 697ab8ce3e8a5b6c033011d3f35d7a79e9b99736 Mon Sep 17 00:00:00 2001 From: Ben Scott Date: Thu, 21 May 2026 13:36:31 -0400 Subject: [PATCH] OSDOCS-17814-RN BMaaS GA release note --- modules/rn-ocp-release-notes-new-features.adoc | 10 +++++++--- modules/rn-ocp-release-notes-technology-preview.adoc | 2 +- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/modules/rn-ocp-release-notes-new-features.adoc b/modules/rn-ocp-release-notes-new-features.adoc index 0b51102e508d..b7c2c89ee990 100644 --- a/modules/rn-ocp-release-notes-new-features.adoc +++ b/modules/rn-ocp-release-notes-new-features.adoc @@ -267,7 +267,7 @@ For more information, see xref:../machine_configuration/machine-configs-custom.a CPU resource enforcement is now enabled by default:: + -With this update, the `system-reserved-compressible` parameter is enabled for all clusters that do not use the reserved CPU feature. This addresses previous issues where the system reserved CPU exceeded the desired limit. This default can be overridden by configuring the `systemReservedCPU: ""` parameter in a kubelet configuration. +With this update, the `system-reserved-compressible` parameter is enabled for all clusters that do not use the reserved CPU feature. This addresses previous issues where the system reserved CPU exceeded the desired limit. This default can be overridden by configuring the `systemReservedCPU: ""` parameter in a kubelet configuration. + For more information, see xref:../nodes/nodes/nodes-nodes-resources-configuring.adoc#system-reserved-compressible_nodes-nodes-resources-configuring[How {product-title} enforces system-reserved CPU]. @@ -285,7 +285,7 @@ For more information, see xref:../nodes/nodes/nodes-nodes-additional-crio-storag Project-scoped image pull secrets for mirrored registries (Technology Preview):: + -With this update, you can pull images from mirrored registries by using project-scoped pull secrets as a technology preview feature. Before this update, you needed to use node-level secrets when pulling from a mirrored registry because the kublet does not recognize the mirror configuration, which is configured at the container-runtime level. +With this update, you can pull images from mirrored registries by using project-scoped pull secrets as a technology preview feature. Before this update, you needed to use node-level secrets when pulling from a mirrored registry because the kublet does not recognize the mirror configuration, which is configured at the container-runtime level. + For more information, see xref:../openshift_images/image-configuration.adoc#images-configuration-registry-mirror-project-secret_image-configuration[Configuring project-scoped image pull secrets for mirrored registries]. @@ -331,9 +331,13 @@ With this release, the Peripheral Component Interconnect (PCI) address for each + For more information, see xref:../installing/installing_bare_metal/bare-metal-postinstallation-configuration.adoc#bmo-about-the-baremetalhost-resource_bare-metal-postinstallation-configuration[About the BareMetalHost resource] and xref:../installing/installing_bare_metal/bare-metal-postinstallation-configuration.adoc#the-baremetalhost-status[The BareMetalHost status]. +{bmaas-first} is generally available:: ++ +With this update, {bmaas-first}, formerly known as Bare Metal as a Service (BMaaS), is generally available. You can provision and manage bare-metal hosts by using the Metal^3^ API and the Bare Metal Operator (BMO). These hosts, external to the {product-title} cluster, can run workloads that might not be suitable for containerization or virtualization, such as legacy applications or applications that require direct hardware access. For more information, see xref:../installing/installing_bare_metal/bare-metal-using-bare-metal-as-a-service.adoc#bare-metal-using-bare-metal-as-a-service[Using {bmaas-first}]. + Expanding bare-metal clusters using OCI images and {bmaas-first} (Technology Preview):: + -With this update, you can expand your bare-metal cluster using {bmaas-first} with images from an OCI registry as a Technology Preview. You can use images from public OCI registries or from the built-in cluster registry. For more information, see xref:../installing/installing_bare_metal/bare-metal-using-bare-metal-as-a-service.adoc[Using Red Hat Bare Metal as a Service for OpenShift]. +With this update, you can expand your bare-metal cluster using {bmaas-first} with images from an OCI registry as a Technology Preview. You can use images from public OCI registries or from the built-in cluster registry. For more information, see xref:../installing/installing_bare_metal/bare-metal-using-bare-metal-as-a-service.adoc#bare-metal-using-bare-metal-as-a-service[Using {bmaas-first}]. [id="ocp-release-notes-scale-and-perform_{context}"] == Scalability and performance diff --git a/modules/rn-ocp-release-notes-technology-preview.adoc b/modules/rn-ocp-release-notes-technology-preview.adoc index 64c3c1d72cd0..cea69af14ef4 100644 --- a/modules/rn-ocp-release-notes-technology-preview.adoc +++ b/modules/rn-ocp-release-notes-technology-preview.adoc @@ -163,7 +163,7 @@ In the following tables, features are marked with the following statuses: |General Availability |General Availability -|Using bare metal as a service +|{bmaas-first} (formerly known as bare metal as a service) |Technology Preview |Technology Preview |General Availability