Remove custom OVN ConfigMap/DataPlaneService workaround for DCN - #1395
Remove custom OVN ConfigMap/DataPlaneService workaround for DCN#1395fultonj wants to merge 1 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
This patch has not yet been tested so please do not merge. |
|
This PR is stale because it has been for over 15 days with no activity. |
|
@gais-ameer I can re-open this patch whenever you need me to. Just let me know. Thanks. |
Remove the custom ovncontroller-config-dcn ConfigMap, ovn-dcn DataPlaneService, and DCN nodeset patching that was working around OVN SB connectivity for DCN compute nodes. The standard OVN service uses DNS (ovsdbserver-sb.openstack.svc) which resolves to internalapi IPs via DNSData CRs. With proper routes in the internalapi NAD, the standard mechanism should work without hardcoding tcp:<IP> entries, which also broke TLS scenarios. The NAD route patching is retained as it is still required for macvlan pods to reach DCN subnets. Tracker: OSPRH-30146 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: John Fulton <fulton@redhat.com>
d5f3dcd to
50c5c56
Compare
fultonj
changed the title
|
@gais-ameer tested DCN adoption with this patch and it succeeded. Thus, I'm re-opening this PR to remove unnecessary tasks. |
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
|
recheck |
2 participants
Remove the custom ovncontroller-config-dcn ConfigMap, ovn-dcn DataPlaneService, and DCN nodeset patching that was working around OVN SB connectivity for DCN compute nodes. The standard OVN service uses DNS (ovsdbserver-sb.openstack.svc) which resolves to internalapi IPs via DNSData CRs. With proper routes in the internalapi NAD, the standard mechanism should work without hardcoding tcp: entries, which also broke TLS scenarios.
The NAD route patching is retained as it is still required for macvlan pods to reach DCN subnets.
Tracker: OSPRH-30146