k8sprocessor: use src IP for further searching if the dst IP is a loopback address #251
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
…pback address Signed-off-by: Daxin Wang <daxinwang@harmonycloud.cn>
NeJan2020
approved these changes
Jun 16, 2022
There was a problem hiding this comment.
This change will not affect the original data(the 'dstIp' field) but simply uses reasoning to determine the true dstPod information. We need to modify some of the existing logic and maintain this principle in the future, that is any reasoning should not change the origin data.
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.
Description
Use src IP for further searching if the dst IP is a loopback address.
Motivation and Context
I found there are some cases where the containers use the loopback address to send requests to the containers in the same pod, such as
node-exporter. In these cases, the destination IP is127.0.0.1with which we can't find the pod information, but the source IP is correct which can be used to search for the destination pod.