-
Notifications
You must be signed in to change notification settings - Fork 3.4k
ci: modify bpftrace script to ignore destinations outside pod CIDRs #36364
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
Conversation
/ci-ipsec-e2e |
1st run of
Also here:
Attaching sysdump for debugging in the other issue cilium-sysdumps.zip. Re-triggering test, the flake is not introduced in this PR. |
2nd run all 🟢 |
/test |
3ac02f0
to
6a4a1d1
Compare
3rd run was green, but need to rebase due to other CI panics. |
/test |
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.
Nice!
One question below. I'm not very familiar with the bpftrace script, so trying to make sure I understand things correctly.
6a4a1d1
to
5124e01
Compare
5124e01
to
a83da4b
Compare
/test |
With this PR, the bpftrace script that we run in CI is now able to ignore TCP traffic with destionation address outside pod CIDRs. This is particularly useful in egress-gateway tests, for which pod-to-world and pod-to-node traffic is sent.
Prior to this, in conformance-ipsec-e2e we used to keep tests separate, and run bpftrace only on non egress-gateway tests.
This PR (re)unifies tests while also running bpftrace in background for all of them.