Value Statement

We are no longer able to validate the kyverno policies that we have in our stable folder.  The kyverno helm chart will not install due to its size and the kyverno operator has not been updated recently so it no longer works with current OCP versions.  ACM can still work well with kyverno and can use kyverno as a policy enforcement point - we just can't consider policies for kyverno "stable" at the moment due to the deployment issue mentioned.

Definition of Done for Engineering Story Owner (Checklist)

• Remove kyverno stable policy doc
• Remove kyverno from stable policy folder in policy-collection and consider adding them to the community folder
• Remove kyverno stable policy from console

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_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

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