-
Notifications
You must be signed in to change notification settings - Fork 370
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
Fix ARP flow not installed issue in networkpolicy-only mode #1575
Conversation
Thanks for your PR. The following commands are available:
|
Codecov Report
@@ Coverage Diff @@
## master #1575 +/- ##
==========================================
+ Coverage 63.31% 64.11% +0.79%
==========================================
Files 170 181 +11
Lines 14250 15188 +938
==========================================
+ Hits 9023 9738 +715
- Misses 4292 4429 +137
- Partials 935 1021 +86
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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, thanks @Dyanngg
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
/test-all |
/test-e2e |
This PR fixes #1572
arpResponderStaticFlow is changed to be installed only in IPv4 mode by #1518, since 'ARP uses broadcast, but IPv6 doesn't support broadcast' #1272 (comment).
However, IsIPv4Enabled() is determined by
c.nodeConfig.PodIPv4CIDR != nil
(pkg/agent/openflow/client.go#L827), and inpka/agent/agent.go
, when networkpolicy-only mode is true, setting nodeConfig.PodIPv4CIDR is skipped:As a result, the arpResponderStaticFlow is never installed for IPv4 networkpolicy-only mode, which causes pods to not able to communicate to apiserver:
This PR fixes this issue by always installing the arpResponderStaticFlow. In IPv6 cases, this flow will simply not get hit.