-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit
*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*
Epic Goal
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.
Scenarios
- 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
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- 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?
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable. - Considerations were made for Extended Update Support (EUS)