-
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
OpenShift SDN: Improvements to UpdateEgressNetworkPolicyRules() #19346
OpenShift SDN: Improvements to UpdateEgressNetworkPolicyRules() #19346
Conversation
@openshift/sig-networking PTAL |
Hm... so had you already written things this way before I pointed you to my ovs-transaction branch? I feel like that way is simpler, and it also has the advantage of automatically improving all uses of ovs-ofctl, without needing any further rewriting... |
Old behavior: 1. Drop outgoing traffic 2. Examine egress np, generate and add ovs flows 3. Enable traffic Step (2) could be slow when egress np has many DNS entries. New behavior: (1) Examine egress np, generate ovs flows (not added) (2) Drop outgoing traffic (3) Add generated ovs flows in (1) (4) Enable traffic
eac29d5
to
d615f22
Compare
@danwinship Current changes on this pr should unblock #19276 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, 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 |
- With ovs atomic transaction, flows are actually executed when Commit() is called so we no longer need the earlier workaround.
- With ovs atomic transaction, flows are actually executed when Commit() is called so we no longer need the earlier workaround.
- With ovs atomic transaction, flows are actually executed when Commit() is called so we no longer need the earlier workaround.
- With ovs atomic transaction, flows are actually executed when Commit() is called so we no longer need the earlier workaround.
- With ovs atomic transaction, flows are actually executed when Commit() is called so we no longer need the earlier workaround.
- With ovs atomic transaction, flows are actually executed when Commit() is called so we no longer need the earlier workaround.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1558484
Fixes #19276