Feature Overview

Today, the Governance UX is primarily driven and keyed off of the deployed policies; e.g. foobar-policy - 4/5 clusters violating the policy.  We lack a UX that provides a more cluster-driven/oriented experience; e.g. list of clusters - 3/5 policies are violated.

Goals

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

• Allow users to understand their governance posture from a cluster / managed cluster set perspective
  • e.g.; what is my governance posture for all clusters running on Azure?
  • e.g.; what is my governance posture for all OpenShift clusters running on 4.17 and below?
  • e.g.; what is my governance posture for all clusters running in production (cluster label env=prod)?

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:

• This data should be based on the same data from Discovered policies (e.g. includes Configuration/Certificate/OperatorPolicy, Gatekeeper, Kyverno, VAPB).
  • Do not base off of the OCM.io Policy kind
• As a user, I can see a list of my clusters, at a high-level, and understand the audit violation status of the policies that are deployed (rough description, can be modified)
  • Table columns:
    • Name (cluster name, just like clusters table) (searchable, sortable)
      • Clickable to details page
    • Namespace (cluster namespace, just like clusters table) (searchable, sortable)
    • Cluster set (ManagedClusterSet, clickable to launch to cluster set details page) (searchable, sortable, filterable)
    • Infrastructure (same as clusters table) (searchable, sortable, filterable)
    • Distribution version (same as clusters table) (searchable - same as clusters table, sortable)
    • Total applied policies ? (sortable)
    • # of policies in violation status (including OCM.io, Gatekeeper, Kyverno, VAP) (sortable)
      • Maybe we can do pills based on the severity?
    • Cluster labels (searchable, filterable)
• As a user, I can drill into a given cluster, and see a list of policies that are applied to the cluster with their respective statuses
  • Should this just be a new tab on the Cluster details page?
    • How would the breadcrumbs work then?
  • Table columns (similar to discovered policies):
    • Name (policy's name)
    • Engine
    • Kind
    • Response action
    • Severity
    • Violations (Violations / No violations)
    • Source
• As a user, I can drill into a given deployed policy on a specific cluster, and see the policy details.
  • Same as existing policy details page
• Remove the Clusters card on the Governance Overview page
• Update the Infrastructure > Cluster details page's Total policy count card to reflect the # policies that would be viewed from the Governance section's policy list page.
  • Make this number clickable to launch to that details view.

Questions to answer

• Should this just be integrated in the Infrastructure > Clusters page
  • No.  The page is full, and it will be simpler and a more focused UX if we just have a dedicated cluster page in the Governance section.
• How does the user get to this page?
  • New tab in Governance?
  • New navigation item under Governance?
  • etc

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