Feature Overview

Overhaul the existing implementation of the Governance overview

Goals

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

• Provide a UX that allows for users to quickly visualize their governance status across the fleet, based on their configured policies and cluster infrastructure
• (TBD) Provide ways to customize the Governance dashboard to tailor to the user's specific needs

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:

• Change RHACM Navigation, make Governance a navigation group (like Home or Infrastructure)
  • Governance
    • Dashboard / Overview
    • Policies
• On "Policies" navigation page, change the order of the page tabs to the following:
  • Discovered policies
  • Policies
  • Policy sets
• Governance Dashboard, some ideas:
  • Keep current Policy set violations card
  • Keep current Policy violations card
  • Remove Clusters card (to be replaced by:  https://issues.redhat.com/browse/ACM-15338 )
  • Remove Standards, Categories, Controls cards
    • Or do we need to support these annotations on the policy template CRs and the other policy engines, and keep the card?
  • Potential new cards:
    • Severity..
      • Audit violations by severity
    • Clusters...
      • Cluster labels with most audit violations (e.g. top 5 or 10)
      • Cluster sets with most audit violations
    • Policy group
      • Violations by policy label (maybe top 5, or do them all)
    • Infrastructure provider
      • Violations by infra provider
    • ???
• Allow for user to apply a combination of label filters similar to the ACM Overview
  • Related:  https://issues.redhat.com/browse/ACM-5276 

Questions to answer

• Can we leverage https://perses.dev/ to enable this dashboard feature; and potentially for user customized dashboards?

Out of Scope

• …

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)?