From 534c68062bcea640ed959d524d7a2a8a02996789 Mon Sep 17 00:00:00 2001 From: dfitzmau Date: Wed, 12 Mar 2025 10:45:06 +0000 Subject: [PATCH] OSDOCS-13634-17: Removed TP notice for customized br-ex bridge --- ...ting-manifest-file-customized-br-ex-bridge.adoc | 7 ------- release_notes/ocp-4-17-release-notes.adoc | 14 +++++++------- 2 files changed, 7 insertions(+), 14 deletions(-) diff --git a/modules/creating-manifest-file-customized-br-ex-bridge.adoc b/modules/creating-manifest-file-customized-br-ex-bridge.adoc index a77c95b84c93..9467bce2248b 100644 --- a/modules/creating-manifest-file-customized-br-ex-bridge.adoc +++ b/modules/creating-manifest-file-customized-br-ex-bridge.adoc @@ -21,17 +21,11 @@ endif::[] ifndef::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[] As an alternative to using the `configure-ovs.sh` shell script to set a `br-ex` bridge on a bare-metal platform, you can create a `MachineConfig` object that includes an NMState configuration file. The NMState configuration file creates a customized `br-ex` bridge network configuration on each node in your cluster. - -:FeatureName: Creating a `MachineConfig` object that includes a customized `br-ex` bridge -include::snippets/technology-preview.adoc[] endif::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[] ifdef::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[] As an alternative to using the `configure-ovs.sh` shell script to set a `br-ex` bridge on a bare-metal platform, you can create a `NodeNetworkConfigurationPolicy` custom resource (CR) that includes an NMState configuration file. The NMState configuration file creates a customized `br-ex` bridge network configuration on each node in your cluster. -:FeatureName: Creating a `NodeNetworkConfigurationPolicy` CR that includes a customized `br-ex` bridge -include::snippets/technology-preview.adoc[] - This feature supports the following tasks: * Modifying the maximum transmission unit (MTU) for your cluster. @@ -46,7 +40,6 @@ Consider the following use cases for creating a manifest object that includes a * You want to make advanced configurations to the bridge that are not possible with the `configure-ovs.sh` shell script. Using the script for these configurations might result in the bridge failing to connect multiple network interfaces and facilitating data forwarding between the interfaces. ifndef::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[] - [NOTE] ==== If you require an environment with a single network interface controller (NIC) and default network settings, use the `configure-ovs.sh` shell script. diff --git a/release_notes/ocp-4-17-release-notes.adoc b/release_notes/ocp-4-17-release-notes.adoc index 4bc7d64366c0..99e12d21b493 100644 --- a/release_notes/ocp-4-17-release-notes.adoc +++ b/release_notes/ocp-4-17-release-notes.adoc @@ -2235,15 +2235,15 @@ In the following tables, features are marked with the following statuses: |Not Available |General Availability -|Configure the `br-ex` bridge needed by OVN-Kuberenetes using NMState +|Configure the `br-ex` bridge needed for OVN-Kubernetes to use NMState |Not Available -|Technology Preview -|Technology Preview +|General Availability +|General Availability -| Overlapping IP configuration for multi-tenant networks with Whereabouts -| Not Available -| General Availability -| General Availability +|Overlapping IP configuration for multi-tenant networks with Whereabouts +|Not Available +|General Availability +|General Availability |User defined network segmentation |Not Available