Skip to content

Conversation

@stuggi
Copy link
Contributor

@stuggi stuggi commented Feb 12, 2026

  • added ctlplane network
  • added optional provider networks with dedicated nic on OCP workers

@stuggi stuggi requested a review from karelyatin February 12, 2026 07:57
@stuggi stuggi force-pushed the fix_network_overview branch from a9b0cce to 600edbc Compare February 12, 2026 08:01
* added ctlplane network
* added optional provider networks with dedicated nic on OCP workers

Signed-off-by: Martin Schuppert <[email protected]>
@stuggi stuggi force-pushed the fix_network_overview branch from 600edbc to da4136b Compare February 12, 2026 08:01
@karelyatin
Copy link
Contributor

@stuggi there is no need to additionally add provider networks on the EDPM node as there is already a external network/Floating IP mentioned there, if want can modify that name to External/Provider networks etc. Reason is the requirement is one ovs bridge per physical network and if we differentiate external / provider networks it may signify two different physical network and in that case we would need multiple bonds and bridges. Also for OCP worker side only external provider network makes sense as those are used for centralized routing and no workload runs on those nodes.
On OCP worker side can connect this same network on nic6 as optional(as Customer can choose to setup EDPM networker node or if there is no requirement for neutron routers/FLoating IPs in that case also there is no need to setup OVS on control plane side)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants