From 739db23d15f2f52278933c3650f8a4ec9bf12d1f Mon Sep 17 00:00:00 2001 From: srir Date: Tue, 10 Mar 2026 13:53:36 +0530 Subject: [PATCH] CNF#22213: Added a recommendation --- modules/telco-core-networking.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/modules/telco-core-networking.adoc b/modules/telco-core-networking.adoc index f3a7224ef2a..3f63b6c0c91 100644 --- a/modules/telco-core-networking.adoc +++ b/modules/telco-core-networking.adoc @@ -56,6 +56,12 @@ For more information, see "Cluster Network Operator". The following diagram illustrates how specific service IP addresses are advertised to the outside via specific VLAN interfaces. Services routes are defined in `BGPAdvertisement` CRs and configured with values for `IPAddressPool1` and `BGPPeer1` fields. -- +.. Define a MetalLB `BGPAdvertisement` CR to specify which IP address pools should be advertised to a selected list of `BGPPeer` resources. The following diagram illustrates how specific service IP addresses are advertised externally through specific VLAN interfaces. Services routes are defined in `BGPAdvertisement` CRs and configured with values for `IPAddressPool1` and `BGPPeer1` fields. + +[NOTE] +==== +Figure 3.2 shows the recommended network topology, where bonding uses ports from the same dual-port NIC. Bonding ports across different NICs is not recommended. +==== .Telco core reference design MetalLB service separation image::openshift-telco-core-rds-metallb-service-separation.png[Telco core reference design MetalLB service separation]