Fix a bug where a TCP connection to a hostNetwork pod could rarely be resolved to the wrong service
#228
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
orishoshan
approved these changes
Jul 25, 2024
omris94
changed the title
hostNetwork pods when creating IP to pod index hostNetwork pod could be resolved to the wrong service
omris94
changed the title
hostNetwork pod could be resolved to the wrong servicehostNetwork pod could rarely be resolved to the wrong service
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Since
hostNetworkpods use the IP of their nodes, it doesn't make sense to use their IPs in this index.