-
Notifications
You must be signed in to change notification settings - Fork 165
fix(networkbaseline): Aggregate external flows in baseline status #15491
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
fix(networkbaseline): Aggregate external flows in baseline status #15491
Conversation
Skipping CI for Draft Pull Request. |
Images are ready for the commit at 673344e. To use with deploy scripts, first |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #15491 +/- ##
=======================================
Coverage 48.68% 48.69%
=======================================
Files 2602 2602
Lines 191486 191501 +15
=======================================
+ Hits 93234 93253 +19
+ Misses 90922 90918 -4
Partials 7330 7330
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
5ed3a0f
to
6233050
Compare
Caution There are some errors in your PipelineRun template.
|
To avoid complex behavior in the aggregation steps, the anonymization of discoverd external flows has been moved to its own component. This means that aggregation can aggregate by name/supernet/timestamp as normal and as a last step, the flows are transformed/anonymized before being added to the graph.
5720584
to
673344e
Compare
/test all |
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.
LGTM !
Description
There is a discrepancy between the flows shown on the network graph and the flows used by the network baseline API, where aggregation has not occurred and therefore it may report duplicate baseline results for a given deployment.
This PR applies the same aggregation method to the baseline API in order to match the graph view.
User-facing documentation
Testing and quality
Automated testing
How I validated my change
Test changes should be sufficient; otherwise manual testing on OCP cluster has confirmed that aggregation is successful and matches the network graph API