Skip to content

OCPBUGS-7205: don't advertise ovn-kubernetes local addresses in mdns#1348

Merged
openshift-merge-robot merged 1 commit intoopenshift:mainfrom
zshi-redhat:mdns-ignore-ovn-address
Feb 22, 2023
Merged

OCPBUGS-7205: don't advertise ovn-kubernetes local addresses in mdns#1348
openshift-merge-robot merged 1 commit intoopenshift:mainfrom
zshi-redhat:mdns-ignore-ovn-address

Conversation

@zshi-redhat
Copy link
Contributor

Signed-off-by: Zenghui Shi zshi@redhat.com

@openshift-ci openshift-ci bot requested review from copejon and fzdarsky February 10, 2023 03:20
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2023
@zshi-redhat zshi-redhat changed the title mdns: don't advertise ovn-kubernetes local addresses OCPBUGS-7205: don't advertise ovn-kubernetes local addresses in mdns Feb 10, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Feb 10, 2023
@openshift-ci-robot
Copy link

@zshi-redhat: This pull request references Jira Issue OCPBUGS-7205, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.0) matches configured target version for branch (4.13.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jogeo

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Signed-off-by: Zenghui Shi zshi@redhat.com

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot requested a review from jogeo February 10, 2023 03:22
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This introduces a dependency between the MDNS and OVN components, which is going to make it harder to make OVN pluggable. We can do this for now, but we need a plan to decouple these again in the future. What can we do to keep them loosely coupled?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm actually doing some code preparation work in this PR to move ovnk related code in its own files under pkg/config/ovn. Before this PR, the ovnk interfaces and special IP address are hardcoded in mdns controller. For fully decoupling ovnk from mdns controller (assuming mdns will stay in microshift main), we would need an interface between microshift and plugins to exchange the mdns related information (this is where the binary/script method in pluggable enhancement would help).

@zshi-redhat zshi-redhat force-pushed the mdns-ignore-ovn-address branch from 5efd666 to 2150b5a Compare February 16, 2023 14:54
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 21, 2023
Signed-off-by: Zenghui Shi <zshi@redhat.com>
@zshi-redhat zshi-redhat force-pushed the mdns-ignore-ovn-address branch from 2150b5a to 4dd7e08 Compare February 22, 2023 01:15
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 22, 2023
@dhellmann
Copy link
Contributor

Let's move ahead with this fix. We will have to think about the MDNS requirements when we split CNI out of the MicroShift binary.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 22, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 22, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhellmann, zshi-redhat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [dhellmann,zshi-redhat]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6458f33 and 2 for PR HEAD 4dd7e08 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 22, 2023

@zshi-redhat: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-rpm-install 4dd7e08 link unknown /test e2e-rpm-install

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit e0c7aa1 into openshift:main Feb 22, 2023
@openshift-ci-robot
Copy link

@zshi-redhat: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-7205 has been moved to the MODIFIED state.

Details

In response to this:

Signed-off-by: Zenghui Shi zshi@redhat.com

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants