Skip to content

Add release note for physicalNetworkName for OVN-Kubernetes secondary networks #89471

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.

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

Open
wants to merge 2 commits into
base: enterprise-4.18
Choose a base branch
from
Open
Changes from 1 commit
Commits
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
8 changes: 8 additions & 0 deletions release_notes/ocp-4-18-release-notes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -956,6 +956,14 @@ You must ensure that the configurations of each `NetworkAttachmentDefinition` CR

You still must restart any workloads that use the network attachment definition for the network changes to take effect for those pods.

[id="ocp-release-notes-networking-ovn-kubernetes-secondary-network-localnet-physical-network-name_{context}"]
==== OVN-Kubernetes secondary network support for sharing a physical network between localnets

When configuring a secondary network that uses the `localnet` topology, you can now specify a physical network name with the `physicalNetworkName` field. By default, this value is set to the name of the localnet. Multiple localnets can share the same physical network.

For more information, see xref:../networking/multiple_networks/secondary_networks/creating-secondary-nwt-ovnk.a
doc#configuration-ovnk-network-plugin-json-object_configuring-additional-network-ovnk[Configuring a secondary network that uses the localnet topology].

[id="ocp-release-notes-nodes_{context}"]
=== Nodes

Expand Down