Set container name empty when multiple containers don't specify ports #238
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
Set container name empty when multiple containers don't specify ports.
Motivation and Context
When there are multiple containers specified in one pod but they don't specify ports listened, we added them to the map using the combination of pod IP and port 0 as the key. This would cause us to find an incorrect container name using pod IP and the listening port. Since there is no method to find the exact container we want, I think we should set the container name to empty in case it makes the final result confusing.
Note that if there is only one container in the pod and it doesn't specify its port, we remain its name since no other containers confuse us.