Skip to content

Commit e046ac1

Browse files
committed
OSDOCS-13634-17: Removed TP notice for customized br-ex bridge
1 parent 5080495 commit e046ac1

File tree

2 files changed

+7
-14
lines changed

2 files changed

+7
-14
lines changed

Diff for: modules/creating-manifest-file-customized-br-ex-bridge.adoc

-7
Original file line numberDiff line numberDiff line change
@@ -21,17 +21,11 @@ endif::[]
2121

2222
ifndef::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[]
2323
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.
24-
25-
:FeatureName: Creating a `MachineConfig` object that includes a customized `br-ex` bridge
26-
include::snippets/technology-preview.adoc[]
2724
endif::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[]
2825

2926
ifdef::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[]
3027
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.
3128

32-
:FeatureName: Creating a `NodeNetworkConfigurationPolicy` CR that includes a customized `br-ex` bridge
33-
include::snippets/technology-preview.adoc[]
34-
3529
This feature supports the following tasks:
3630

3731
* 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
4640
* 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.
4741
4842
ifndef::postinstall-bare-metal-ipi,postinstall-bare-metal-upi[]
49-
5043
[NOTE]
5144
====
5245
If you require an environment with a single network interface controller (NIC) and default network settings, use the `configure-ovs.sh` shell script.

Diff for: release_notes/ocp-4-17-release-notes.adoc

+7-7
Original file line numberDiff line numberDiff line change
@@ -2235,15 +2235,15 @@ In the following tables, features are marked with the following statuses:
22352235
|Not Available
22362236
|General Availability
22372237

2238-
|Configure the `br-ex` bridge needed by OVN-Kuberenetes using NMState
2238+
|Configure the `br-ex` bridge needed for OVN-Kubernetes by using NMState
22392239
|Not Available
2240-
|Technology Preview
2241-
|Technology Preview
2240+
|General Availability
2241+
|General Availability
22422242

2243-
| Overlapping IP configuration for multi-tenant networks with Whereabouts
2244-
| Not Available
2245-
| General Availability
2246-
| General Availability
2243+
|Overlapping IP configuration for multi-tenant networks with Whereabouts
2244+
|Not Available
2245+
|General Availability
2246+
|General Availability
22472247

22482248
|User defined network segmentation
22492249
|Not Available

0 commit comments

Comments
 (0)