-
Notifications
You must be signed in to change notification settings - Fork 3.4k
daemon: Do not require socketLB for BPF masq #33728
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
Merged
Merged
Conversation
This file contains hidden or 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
/ci-e2e |
1 similar comment
/ci-e2e |
b85338b
to
01e4049
Compare
/ci-e2e |
Previously, we required socketLB to be enabled in order for BPF masquerade to properly function. The reasoning was outlined in [1] and [2]. As pointed by Julian Wiedmann, [3] resolved the following NAT reply issue: On the remote node, the reply (dst=the client node IP) gets masqueraded by the BPF-masq feature, because we masquerade pod -> remote host IP in the tunnel mode (see comment in the "snat_v4_needed()" for the reason), and currently we don't consult the CT map to see whether a packet is reply. Thus, we can remove the check. [1]: #15437 [2]: 50e59c3 [3]: #17168 Signed-off-by: Martynas Pumputis <m@lambda.lt>
01e4049
to
a45c5de
Compare
/ci-e2e |
/test |
julianwiedmann
approved these changes
Jul 11, 2024
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.
Thank you! Let's see if the reasoning still holds true ...
viktor-kurchenko
approved these changes
Jul 11, 2024
ldelossa
approved these changes
Jul 15, 2024
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.
Review the history of this issue.
Change LGTM.
julianwiedmann
added a commit
to julianwiedmann/cilium
that referenced
this pull request
Jul 16, 2024
This was addressed in cilium#33728. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jul 18, 2024
This was addressed in #33728. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/datapath
Impacts bpf/ or low-level forwarding details, including map management and monitor messages.
backport-done/1.16
The backport for Cilium 1.16.x for this PR is done.
feature/snat
Relates to SNAT or Masquerading of traffic
feature/socket-lb
Impacts the Socket-LB part of Cilium's kube-proxy replacement.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/misc
This PR makes changes that have no direct user impact.
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.
Previously, we required socketLB to be enabled in order for BPF masquerade to properly function. The reasoning was outlined in [1] and [2].
As pointed by Julian Wiedmann, [3] resolved the following NAT reply issue:
Thus, we can remove the check.
[1]: #15437
[2]: 50e59c3
[3]: #17168
Fix #15437
Fix #12699