Remove custom OVN ConfigMap/DataPlaneService from DCN docs - #1394
Merged
openshift-merge-bot[bot] merged 1 commit intoMay 15, 2026
Merged
Conversation
klgill
requested changes
May 14, 2026
klgill
left a comment
klgill
left a comment
Contributor
There was a problem hiding this comment.
I have one very minor edit.
| * Central site nodes reference `subnet1` for all networks. | ||
|
|
||
| . Create an `OpenStackDataPlaneNodeSet` CR for DCN1 edge site compute nodes. You must add inter-site routes to the network configuration template and use the `ovn-dcn` service: | ||
| . Create an `OpenStackDataPlaneNodeSet` CR for DCN1 edge site compute nodes. You must add inter-site routes to the network configuration template: |
Contributor
There was a problem hiding this comment.
Suggested change
| . Create an `OpenStackDataPlaneNodeSet` CR for DCN1 edge site compute nodes. You must add inter-site routes to the network configuration template: | |
| . Create an `OpenStackDataPlaneNodeSet` CR for DCN1 edge site Compute nodes. You must add inter-site routes to the network configuration template: |
Remove documentation for the ovncontroller-config-dcn ConfigMap, ovn-dcn DataPlaneService, and instructions to replace the ovn service with ovn-dcn in DCN nodesets. The adoption should work without these extra steps. The standard OVN service uses DNS (ovsdbserver-sb.openstack.svc) which resolves to internalapi IPs via DNSData CRs and should work for DCN nodes when proper inter-site routes are configured. Jira: OSPRH-30146 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: John Fulton <fulton@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-merge-bot
Bot
merged commit May 15, 2026
7c98be1
into
openstack-k8s-operators:main
6 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove documentation for the ovncontroller-config-dcn ConfigMap, ovn-dcn DataPlaneService, and instructions to replace the ovn service with ovn-dcn in DCN nodesets. The adoption should work without these extra steps.
The standard OVN service uses DNS (ovsdbserver-sb.openstack.svc) which resolves to internalapi IPs via DNSData CRs and should work for DCN nodes when proper inter-site routes are configured.
Jira: OSPRH-30146