Value Statement

After ACM-13278, the Gatekeeper constraints will be indexed as desired. This can then build on the discovered policies table for Open Cluster Management policies in ACM-13337 to show Gatekeeper constraints. This provides the value of the existing ACM integration with Gatekeeper without the user having to deploy the Gatekeeper constraint through an ACM policy.

Definition of Done for Engineering Story Owner (Checklist)

• Gatekeeper constraints are showed in the "Discovered policies" table
• The list view per cluster of the constraint shows the violations like OCM policies except that this is based on if there are audit violations
• The list view per cluster has the following columns:
  • Cluster - a link to the existing policy template details page for that specific policy
  • Response action (generic term for spec.enforcementAction)
    • The default is "deny" if not specified
  • Violations
    • The total number of audit violations
  • Source
  • Severity
    • Should contain a tooltip explaining "This value comes from the policy.open-cluster-management.io/severity annotation on the Gatekeeper constraint"

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.