-
Notifications
You must be signed in to change notification settings - Fork 366
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
Update the network flow visibility doc #1535
Update the network flow visibility doc #1535
Conversation
Thanks for your PR. The following commands are available:
|
As Flow Exporter supports adding network policy information, we need to update the user doc.
de7a59b
to
a7e08ac
Compare
Codecov Report
@@ Coverage Diff @@
## master #1535 +/- ##
===========================================
- Coverage 63.31% 41.00% -22.32%
===========================================
Files 170 105 -65
Lines 14250 12655 -1595
===========================================
- Hits 9023 5189 -3834
- Misses 4292 6999 +2707
+ Partials 935 467 -468
Flags with carried forward coverage won't be shown. Click here to find out more.
|
docs/network-flow-visibility.md
Outdated
the flow record from the destination Node, where the destination Pod resides. Due | ||
to this we miss key information such as destination Pod info, ingress NetworkPolicy | ||
info, stats from the destination Node, etc. In the future, this behavior will be | ||
changed when we add the support for the correlation of the flow records that belong |
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.
when we add support for correlating the different flow records (from source and destination Nodes) that belong to the same flow
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.
I edited the file directly, hope you don't mind
/skip-all |
As Flow Exporter supports adding network policy information,
we need to update the user doc.