Business Problem:

When multiple deployments have the same underlying image, image-related violations will be emitted for every single deployment. While this is helpful, in some cases, like ACSCS where we have dozens of namespaces with almost identical deployments, this just generates noise that is hard to deal with.

Use Cases:

• I might prefer not to be be alerted for the same image-related problem identified in various deployments.
• When I look at the violations page, there is no known to me way to group (not filter!) violations based on some somewhat advanced properties, like "same image", "same namespace", etc.

An example.

943 CVEs from a CSV report. The number is overwhelming, but when properly aggregated, only a few images are affected.

Benefits:

Improves the violation resolution workflows and reduces noise.