-
Bug
-
Resolution: Done
-
Normal
-
rhos-18.0 FR 2 (Mar 2025)
-
None
-
3
-
False
-
-
False
-
?
-
None
-
-
-
Moderate
With BGP L3 at controlplane, OCP nodes do not need to connect to the controlplane network directly/physically, but they connect to EDPM nodes using the BGP networks instead, so the controlplane interface has to be removed from NNCP configuration.
We changed this on our CI job configurations (notice changes on lib/nncp-l3/ocp_node_template.yaml file):
https://github.com/openstack-k8s-operators/architecture/pull/540
We need to adapt BGP docs accordingly.
- Section "5.2.2. Preparing RHOCP with isolated network interfaces for BGP", step 4
- the item corresponding to "ctlplane interface" has to be removed.
- the item corresponding to "Octavia vlan host interface" has to be removed because it uses the same physical interface enp7s0 (RHOSO does not support octavia with BGP yet)
- Remove this: "You can optionally dedicate a NIC to the ctlplane network, and a NIC dedicated to Octavia"
- Section "6.2. Creating the control plane", step 4
- "Compute service (nova)" item: remove the ctlplane networkAttachment. It should not be used.
- "Telemetry service" item: remove the ctlplane networkAttachment and line "dataplaneNetwork: ctlplane" too.
- Section "6.3. Example OpenStackControlPlane CR"
- similar changes to previous section
- Section "7.4.1. Creating the BareMetalHost CRs for unprovisioned nodes"
- TODO: I have doubts about the references to "ctlplane" included in this section
NOTE: all references to ctlplane included in dataplane sections are correct. A ctlplane network needs to be configured on the EDPM nodes, although the controlplane traffic between EDPM nodes and RHOSO pods (running on OCP nodes) is routed through the BGP networks.