Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bpf: egressgw: set trace reason for reply traffic #27218

Merged
merged 1 commit into from Aug 3, 2023
Merged

bpf: egressgw: set trace reason for reply traffic #27218

merged 1 commit into from Aug 3, 2023

Conversation

julianwiedmann
Copy link
Member

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.

@julianwiedmann julianwiedmann added sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages. area/monitor Impacts monitoring, access logging, flow logging, visibility of datapath traffic. release-note/misc This PR makes changes that have no direct user impact. feature/egress-gateway Impacts the egress IP gateway feature. labels Aug 2, 2023
@julianwiedmann
Copy link
Member Author

/test

@julianwiedmann
Copy link
Member Author

/test

@julianwiedmann julianwiedmann marked this pull request as ready for review August 2, 2023 14:54
@julianwiedmann julianwiedmann requested a review from a team as a code owner August 2, 2023 14:54
@julianwiedmann
bpf: egressgw: set trace reason for reply traffic
c3ba5b1 
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
Copy link
Member Author

/test

@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Aug 3, 2023
@julianwiedmann julianwiedmann merged commit f4098db into cilium:main Aug 3, 2023
59 checks passed
@julianwiedmann julianwiedmann deleted the 1.15-bpf-egressgw-reason branch August 3, 2023 07:39
@julianwiedmann julianwiedmann mentioned this pull request Aug 16, 2023
Merged
3 tasks
@julianwiedmann julianwiedmann added the backport-pending/1.14 The backport for Cilium 1.14.x for this PR is in progress. label Aug 16, 2023
@julianwiedmann julianwiedmann mentioned this pull request Aug 16, 2023
Merged
2 tasks
@julianwiedmann julianwiedmann added backport-pending/1.13 The backport for Cilium 1.13.x for this PR is in progress. backport-done/1.13 The backport for Cilium 1.13.x for this PR is done. backport-done/1.14 The backport for Cilium 1.14.x for this PR is done. and removed backport-pending/1.13 The backport for Cilium 1.13.x for this PR is in progress. backport-pending/1.14 The backport for Cilium 1.14.x for this PR is in progress. labels Aug 16, 2023
This was referenced Sep 9, 2023
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jibi jibi jibi approved these changes

Assignees
No one assigned
Labels
area/monitor Impacts monitoring, access logging, flow logging, visibility of datapath traffic. backport-done/1.13 The backport for Cilium 1.13.x for this PR is done. backport-done/1.14 The backport for Cilium 1.14.x for this PR is done. feature/egress-gateway Impacts the egress IP gateway feature. 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. sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@julianwiedmann @jibi