-
Notifications
You must be signed in to change notification settings - Fork 42.1k
[kube-proxy/ipvs] Add flag to enable strict ARP #75295
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
[kube-proxy/ipvs] Add flag to enable strict ARP #75295
Conversation
|
Hi @lbernail. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
|
/ok-to-test /assign @thockin for API review. |
|
/test pull-kubernetes-kubemark-e2e-gce-big |
thockin
left a comment
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.
I'll approve, but @m1093782566 holds LGTM
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lbernail, thockin The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm Thanks @lbernail for contributing IPVS 👍 |
…5-upstream-release-1.13 Automated cherry pick of #75295 upstream release 1.13
…5-upstream-release-1.14 Automated cherry pick of #75295 upstream release 1.14
strict ARP flag was added by kubernetes/kubernetes#75295 It's disable by default to not break some CNI, including flannel so we leave it off by default We must enable it for MetalLB to work metallb/metallb#153 (comment) so fail MetalLB roles if it's not enabled
What type of PR is this?
/kind bug
Not exactly a bug but a regression for some users which use CNI plugins not compatible with this change.
What this PR does / why we need it:
#70530 introduced a change to avoid answering ARP queries for addresses bound to kube-ipvs0 (this broke some setups). However some CNI plugins use unnumbered ptp links between containers and host and this change breaks ARP for them. This PR adds a flag to control this behavior. It's not enabled by default to avoid breaking existing setups when upgrading (not that if a user has run a version that configures the sysctls they will need to change it back, kube-proxy won't do it).
Which issue(s) this PR fixes:
Fixes #71555
Fixes #72779
Not for reviewers:
We discussed alternatives in both issues (see above) and this one seems the best trade-off:
It's the first I'm adding a flag so I may have have missed something. I tried to find a flag name that was clear and not too long but we can change it of course.
Does this PR introduce a user-facing change?:
/sig network
/area ipvs
/assign @m1093782566
cc @kvaps