[v1.14] bpf: EgressGW-related tracing improvements #27524
Merged
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
maintainer-s-little-helper
bot
added
backport/1.14
|
/test-backport-1.14 |
julianwiedmann
force-pushed
the
v1.14-bpf-tracing
branch
from
d342f4d
to
e91a96d
Compare
|
/test-backport-1.14 |
julianwiedmann
force-pushed
the
v1.14-bpf-tracing
branch
from
e91a96d
to
2f7c475
Compare
|
/test-backport-1.14 |
julianwiedmann
force-pushed
the
v1.14-bpf-tracing
branch
from
2f7c475
to
3e06e8f
Compare
|
/test-backport-1.14 |
|
/ci-verifier |
julianwiedmann
force-pushed
the
v1.14-bpf-tracing
branch
from
250d0a0
to
c6dca97
Compare
|
/ci-verifier |
julianwiedmann
force-pushed
the
v1.14-bpf-tracing
branch
from
c6dca97
to
3361de3
Compare
|
/ci-verifier |
[ upstream commit 93c8884 ] [ backporter's note: Looks a bit different, as the v1.14-stable branch doesn't have the SNAT split from cilium#26674. ] Right now this is decided at the lowest level of the SNAT path. But actually the callers know much better. In particular this avoids one case where we bake EgressGW knowledge deep into the SNAT code. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
[ upstream commit 3796d0d ] When the NAT code creates a CT entry for a SNATed connection (for instance for EgressGW traffic), pass back the resulting trace information to tail_handle_snat_fwd_ipv*(). Note that this also wires up the path from tail_nodeport_nat_egress_ipv*(), but those connections never require CT on the NAT level. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
[ upstream commit f4098db ] When redirecting EgressGW replies to the tunnel interface, we don't have a CT lookup to determine the trace reason. But we still know it's a reply, so we can set the reason manually. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
julianwiedmann
force-pushed
the
v1.14-bpf-tracing
branch
from
3361de3
to
5f4e7c2
Compare
|
/test-backport-1.14 |
|
Needed a backport of #27079 to reduce stack size :/. |
gentoo-root
approved these changes
Aug 18, 2023
julianwiedmann
added
the
ready-to-merge
joestringer
approved these changes
Aug 21, 2023
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.
Manual backport (due to complexity troubles and smaller contextual conflicts) of
Once this PR is merged, you can update the PR labels via:
or with