initial eBPF packet capture implementation #50
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
|
I confirm I was able to see this in action. |
|
Every now and then, Hub and Front break. |
|
Created additional channel for non-TLS traffic, so TLS is tagged properly |
alongir
approved these changes
Apr 15, 2024
There was a problem hiding this comment.
@mertyildiran I tested the new images and compared to previous images. I feel comfortable with this as-is. I will obviously run more tests when we release a canary version. t will be good if you can go over the code.
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.
initial support for capturing packets via eBPF
this change starts capturing packets in case is cgroups V2 is active on the host node
command-line parameter
-disable-ebpfcan be applied to disable the functionality