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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
connlist implementing exposure analysis #296
connlist implementing exposure analysis #296
Changes from 1 commit
813ee12
d7542ba
fc3e814
6a2215e
5ab1fb5
4b1aefb
1b295dc
4237e81
59b0477
63e8f68
bdf6d95
bb07eac
cd0743a
b419627
995be16
f979481
f9745ba
c210b05
77fbee6
d6c8101
9e154f0
3f3f080
53c4d72
2aeb9a8
4f451bf
36f370d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of refining the list of ingressExposure/egressExposure only in a later stage, we could have here a map from "representative" pod name to its connection-set (instead of a list), and store in the map the larges connection-set object each time we assign in the same entry, so that this would prevent possible duplication that later has to be refined.
This requires changing the internal type from list to map , so should consider if we want to apply such change, in a next branch / sub task..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated a new sub-task
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which sub-task?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.