Add support for SockLB events #816
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
gandro
added
the
release-note/major
chancez
reviewed
Nov 16, 2022
I would argue they should. The service IP is not visible anywhere otherwise. Before SockLB was a thing, Hubble would show the clusterIP in |
michi-covalent
approved these changes
Nov 17, 2022
chancez
approved these changes
Nov 18, 2022
|
Somehow GitHub seems to be stuck on the status checks. Closing an re-opening. |
gandro
force-pushed
the
pr/gandro/trace-socklb-events
branch
from
1a5b658
to
fb779fc
Compare
This pulls in the new Hubble API definitions for SockLB events. Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
This adds support for Trace SockLB events. These events are similar to L3/L4 trace events, but are traced on the socket level. This means they have a few differences to regular trace events: - There are events for pre- and post-translation. This means that we now get visibility into the service load balancing, meaning that source/destination service is populated before NAT/after rev-NAT. - These events do not contain the source port or packet related details (such as TCP flags, Ethernet headers etc). - Because the events are emitted on a socket level, there is no meaningful traffic direction or reply status. The reply status and traffic direction of the trace sock events is unknown. - These events have two verdicts: TRACED and TRANSLATED. The former is used when ever the SockLB BPF hook is executed, the latter is additionally emitted if NAT or reverse NAT has been applied. Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
gandro
force-pushed
the
pr/gandro/trace-socklb-events
branch
from
fb779fc
to
9dfd1d5
Compare
kaworu
approved these changes
Nov 21, 2022
maintainer-s-little-helper
bot
added
the
ready-to-merge
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.
This adds support for Trace SockLB events. These events are similar to L3/L4 trace events, but are traced on the socket level. This means they have a few differences to regular trace events:
Here is an example of
pod-to-apod doing a service lookup for theecho-aservice (first the DNS lookup against kubedns, then a TCP connection to theecho-aservice):