search

goharbor / harbor

An open source trusted cloud native registry project that stores, signs, and scans content.
https://goharbor.io
Apache License 2.0
23.97k stars 4.74k forks source link

Repository specific CVE whitelisting #16688

Open geowalrus4gh opened 2 years ago

geowalrus4gh commented 2 years ago

We are having multiple repositories in a single Harbor project. Container images for different applications are separated by paths. Currently its is only possible for adding white list for all the images together in a project specific whitelist. We are forced to create multiple projects for multiple container images which is restricting us to define common policies and configurations to all artifacts.

We would like to have repository specific whitelisting configuration which will ease the management of CVEs.

A possible solution : Add pattern matching facility (like what it is done in tag retention policies etc.) in the whitelisting page.

github-actions[bot] commented 2 years ago

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

qnetter commented 2 years ago

Pattern matching sounds like a good generalized solution for which this is one use case. It is not likely to fit in the next release, but should be planned into the backlog.