You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many harbor instances have Terabytes of data and, 10000 thousand artifacts.
This results in vulnerability scans that run for days or weeks.
Describe the solution you'd like
The user should be able to do policy-based regular vulnerability scans, where the user can decide based on criteria what images should be rescanned.
Here are some examples:
include/exclude
Artifacts pulled within the last [n] days?
Artifacts pushed [n] days ago
All matching [rx] regex
All with label [l]
Describe the main design/architecture of your solution
So instead of having a huge job that is running across the whole registry, there should be a policy in place the allow to run multiple smaller jobs for different types of images.
Additional context
The idea is to have a similar use experience as with retention, immutability and replication polices.
The text was updated successfully, but these errors were encountered:
Many harbor instances have Terabytes of data and, 10000 thousand artifacts.
This results in vulnerability scans that run for days or weeks.
Describe the solution you'd like
The user should be able to do policy-based regular vulnerability scans, where the user can decide based on criteria what images should be rescanned.
Here are some examples:
include/exclude
Describe the main design/architecture of your solution
So instead of having a huge job that is running across the whole registry, there should be a policy in place the allow to run multiple smaller jobs for different types of images.
Additional context
The idea is to have a similar use experience as with retention, immutability and replication polices.
The text was updated successfully, but these errors were encountered: