Business Problem:

When I inspect deployments on the risk page, I might decide to postpone or exclude deployments, entire namespaces or maybe even clusters. It seems I can't do it today.

Overall, it feels that most of the actions one can do for CVEs and violations (search, snooze, resolve, bulk mode) also apply to risk entries.

Use Cases:

A few examples:

• I've investigated some risky deployment and convinced myself there is nothing we can do at this point however I've started an off-the-band process to have necessary changes made. I'd like now to remove the deployment from the main view but record some sort of a reminder to come back and verify later. An associated message would be great.
• I've observed that quite a few risky deployments come from a specific namespace. While this is being investigated or maybe because the entire namespace is not important (say, an isolated sandbox), I'd like to remove everything from this namespace from the main view.

Benefits:

Simplifies the process of risk management and reduces noise.