Feature Overview

In the Discovered policies UX, resource violations from any of the supported policy engines can only be viewed in a given single cluster.  We need to provide a view that supports being able to see all of the resource violations for a given policy across all the clusters it is applied to.

Goals

This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature

• Provide a UX that allows users to see resource violations for a policy across all applied clusters

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases

This Section:

• As an Open Cluster Management user; I can see the related resource results and violations across multiple clusters from a single view
• As a Gatekeeper user, I can see the related resource results and violations across multiple clusters from a single view
• As a Kyverno user, I can see the related resource results and violations across multiple clusters from a single view
• Allow users to search, filter, and sort the table by relevant column parameters

Questions to answer

• What are the potential scalability implications on search for supporting this?
  • e.g. Policy is auditing configuration on pods; and the policy is applied across many clusters; will this cause stress on search?
• What filtering capabilities should this support to allow for a more scalable UX when there are many resource violations?
  • Filtering on cluster name, namespace, etc?

Out of Scope

• ValidatingAdmissionPolicy is not applicable for this work currently

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?