Skip to content

Commit 05e00af

Browse files
authored
Merge pull request #94606 from dfitzmau/OSDOCS-14925
OSDOCS-14925: Documented the slb mode release note
2 parents 247ef86 + b103340 commit 05e00af

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

release_notes/ocp-4-19-release-notes.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -782,6 +782,11 @@ For more information, see xref:../updating/preparing_for_updates/updating-cluste
782782
==== Updates to Gateway API custom resource definitions (CRDs)
783783
{product-title} {product-version} updates {SMProductName} to version 3.0.2, and Gateway API to version 1.2.1. See the link:https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.0/html/release_notes/ossm-release-notes[{SMProductShortName} 3.0.0 release notes] and the link:https://github.com/kubernetes-sigs/gateway-api/blob/main/CHANGELOG/1.2-CHANGELOG.md#v121[Gateway API 1.2.1 changelog] for more information.
784784

785+
[id="ocp-4-19-networking-balance-slb-mode_{context}"]
786+
==== Enable OVS balance-slb mode for your cluster (General Availability)
787+
788+
You can enable the Open vSwitch (OVS) `balance-slb` mode on infrastructure where your cluster runs so that two or more physical interfaces can share their network traffic. For more information, see xref:../installing/installing_bare_metal/ipi/ipi-install-installation-workflow.adoc#enabling-OVS-balance-slb-mode_ipi-install-installation-workflow[Enabling OVS balance-slb mode for your cluster].
789+
785790
[id="ocp-4-19-networking-ptp-dual-oc_{context}"]
786791
==== Dual-port NICs for improved redundancy in PTP ordinary clocks (Technology Preview)
787792
With this release, you can use a dual-port network interface controller (NIC) to improve redundancy for Precision Time Protocol (PTP) ordinary clocks.
@@ -804,7 +809,7 @@ With this release, {product-title} introduces the Data Processing Unit (DPU) Ope
804809
Administrators can now use the `ClusterUserDefinedNetwork` custom resource to deploy secondary networks on a `Localnet` topology. This feature allows pods and virtual machines connected to the localnet network to egress to the physical network. For more information, see xref:../networking/multiple_networks/primary_networks/about-user-defined-networks.adoc#nw-cudn-localnet[Creating a ClusterUserDefinedNetwork CR for a Localnet topology].
805810

806811
[id="ocp-4-19-port-isolation-linux-bridge_{context}"]
807-
==== Enable port isolation for a Linux bridge NAD
812+
==== Enable port isolation for a Linux bridge NAD (Generally Available)
808813

809814
You can enable port isolation for a Linux bridge network attachment definition (NAD) so that virtual machines (VMs) or pods that run on the same virtual LAN (VLAN) can operate in isolation from one another. For more information, see xref:../virt/vm_networking/virt-connecting-vm-to-linux-bridge.adoc#virt-linux-bridge-nad-port-isolation_virt-connecting-vm-to-linux-bridge[Enabling port isolation for a Linux bridge NAD].
810815

0 commit comments

Comments
 (0)