Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSDOCS-13634-17: Removed TP notice for customized br-ex bridge #90133

Merged
merged 1 commit into from
Mar 13, 2025
Merged

OSDOCS-13634-17: Removed TP notice for customized br-ex bridge #90133

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 0 additions & 7 deletions modules/creating-manifest-file-customized-br-ex-bridge.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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.
Expand Down
14 changes: 7 additions & 7 deletions release_notes/ocp-4-17-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down