Automated cherry pick of #4419: Set NO_FLOOD to IPsec tunnel ports #4470: Fix that Service routes may get lost when starting on Windows #4654: Restore NO_FLOOD to OVS ports after reconnecting the OVS #4711: Fix route deletion for Service ClusterIP and LoadBalancerIP #4759
Conversation
This file contains 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
Set NO_FLOOD to IPsec tunnel ports to avoid ARP flooding. Signed-off-by: Xu Liu <xliu2@vmware.com>
Fix antrea-io#4467 Signed-off-by: Hongliang Liu <lhongliang@vmware.com>
The NO_FLOOD configuration is lost when the OVS daemon is restarted. Currently, the only way to recover this configuration is by restarting the agent. This pull request adds logic to recover the configuration when receiving OVS reconnection events. Signed-off-by: Xu Liu <xliu2@vmware.com>
luolanzone
added
the
kind/cherry-pick
Codecov Report
@@ Coverage Diff @@
## release-1.7 #4759 +/- ##
================================================
- Coverage 61.76% 40.39% -21.38%
================================================
Files 298 258 -40
Lines 44437 39306 -5131
================================================
- Hits 27446 15877 -11569
- Misses 14803 21907 +7104
+ Partials 2188 1522 -666
Flags with carried forward coverage won't be shown. Click here to find out more.
|
luolanzone
force-pushed
the
automated-cherry-pick-of-#4419-#4470-#4654-#4711-upstream-release-1.7
branch
from
eea9bb8
to
49f98bd
Compare
When proxyAll is enabled, AntreaProxy needs to install routes in the host network namespace to redirect traffic to OVS for load balancing. For a Service with multiple ports, multiple ServicePorts are generated and processed. The previous code installed the route for a ClusterIP or a LoadBalancerIP multiple times when such a Service was created, and uninstalled the route multiple times when it was deleted, leading to a few problems. This patch adds a serviceIPRouteReferences which tracks the references of Service IPs' routes. The key is the Service IP and the value is the the set of ServiceInfo strings. With the references, we install a route exactly once as long as it's used by any ServicePorts and uninstall it exactly once when it's no longer used by any ServicePorts. This patch also fixes an issue that the route for ClusterIP was not removed on Windows Nodes after the Service was removed. Fixes antrea-io#4361 Signed-off-by: Quan Tian <qtian@vmware.com>
luolanzone
force-pushed
the
automated-cherry-pick-of-#4419-#4470-#4654-#4711-upstream-release-1.7
branch
from
49f98bd
to
4ffe36b
Compare
luolanzone
deleted the
automated-cherry-pick-of-#4419-#4470-#4654-#4711-upstream-release-1.7
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cherry pick of #4419 #4470 #4654 #4711 on release-1.7.
#4419: Set NO_FLOOD to IPsec tunnel ports
#4470: Fix that Service routes may get lost when starting on Windows
#4654: Restore NO_FLOOD to OVS ports after reconnecting the OVS
#4711: Fix route deletion for Service ClusterIP and LoadBalancerIP
For details on the cherry pick process, see the cherry pick requests page.