Feature Overview

Add a column to the Discovered policies table to display the labels on the policy and add a filtering capability to the table

Goals

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

• Help users organize their policies and be able to quickly navigate through them at scale.
• Correcting a feature gap with Discovered policies, policy grouping was essentially lost; because both Policy kind and PolicySet kind provide grouping constructs; this issue is meant to fill the feature gap between our Policy framework pattern and other alternative deployment options (like Argo CD).  Grouping by labels is a logic and common pattern in Kube.

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 a policy user, I want to be able to organize my different policies through Kubernetes labels
  • On Discovered policies table, user can view the labels associated with a given policy (first page level)
  • When drilling into a specific policy, the labels should also be shown for each cluster row of the policy instnace (second page level)
    • This is due to the potential issue of differing labels between them (because Discovered policies is aggregating by name and Kind)
  • On the policy details page; the labels should be displayed in the details card (third page level)
• As a policy user, I want to be able to filter the table by the desired/undesired labels on the policy
• Support query parameter in URL for applied label filtering; to allow for easy linking and sharing

Questions to answer

• Discovered policies table is aggregating by the policy Name and Kind.  Some policies may have slight variations in labels; what should the table do?
  • Aggregate across all, and then display the labels per policy instance on the details page?

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