-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate egress IP tracking code to pkg/network/common #20155
Migrate egress IP tracking code to pkg/network/common #20155
Conversation
01f9724
to
8b5fbbe
Compare
90f7d66
to
afd9049
Compare
afd9049
to
7e850d2
Compare
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, dcbw, pravisankar The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
/test cross |
/retest |
1 similar comment
/retest |
Prelude to master-side egress IP tracking; the master will need to be doing the same egressIP-tracking that the node does, so move the code to pkg/network/common so they can share it.
pkg/network/common/egressip_test.go is mostly just a copy of pkg/network/node/egressip_test.go, with the "netlink" and "OVS" changes squished together into a single change stream, and the comments changed in a few places to reflect the fact that "local node" vs "remote node" doesn't matter to the common code.
The changes at the end of pkg/network/node/egressip_test.go are because if egressIPWatcher deletes OVS flows and then recreates them, the testing code requires that we call
assertOVSChanges
rather thanassertNoOVSChanges
even if the new flows are identical to the old ones. The new code doesn't delete and recreate flows when nothing changed, so we don't need to do that now.