Conversation
|
Skipping CI for Draft Pull Request. |
|
Images are ready for the commit at 4325688. To use with deploy scripts, first |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #12930 +/- ##
==========================================
+ Coverage 48.27% 48.29% +0.01%
==========================================
Files 2450 2450
Lines 176664 176641 -23
==========================================
+ Hits 85290 85308 +18
+ Misses 84520 84478 -42
- Partials 6854 6855 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
9f90570 to
e451e2e
Compare
40e0675 to
27255c3
Compare
|
@RTann: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Description
Prior to this change, we'd run into an issue when we may add support for new distributions or perhaps even change how old distributions are represented in the vuln table (this happened when we added VEX support - #12452).
When users update to the latest version, they will get a note saying we do not support an OS, when, in fact, we do. This notice will go away after the next update (hopefully), but that is currently in 24 hours.
This change hopes to prevent any questions about OS support, and it updates the list of known distributions upon each update.
This puts more load on the database, as there will be more reads, but it prevents any misunderstandings about which OSes we support
User-facing documentation
Testing and quality
Automated testing
How I validated my change
CI + deployed to a cluster. CPU usage seems ok to me