Epic Goal

• In our PolicyCollectionRepository we already have all the Policies we want to bring into a PolicySet for OpenShiftPlus.
  this Jira is about to make the Policies stable:
  https://github.com/stolostron/policy-collection/tree/main/policygenerator/policy-sets/community/openshift-plus
• we need automated tests to make this OPP PolicySet 'stable' and supported

Why is this important?

• it's part of our strategy to configure OpenShift+ with Policies/PolicySets
•  

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
  • PolicySet must become Compliant
  • OPP products must be deployed
  • Automation must be able to run when products in OPP release a new version
    • z-streams should be taken into consideration for this, but the main goal is just the continuous validation that the PolicySet deploys OPP successfully
  • The use of the DevSecOps validated pattern does not achieve the goal here unless the OPP PolicySet can be deployed and validated alongside.  That has not been attempted and conflicts could exist if both are deployed.
  •  
• Release Technical Enablement - Provide necessary release enablement details and documents.
  • Policy documentation in the ACM user's guide specific to this policy set
  • Documentation in the policy-collection repository for this policyset

Full OPP product interop testing is desired for OPP in general, but is not required for this EPIC which is focused on a best practices deployment of OPP

Dependencies (internal and external)

1. https://issues.redhat.com/browse/INTEROP-5280 – OPP testing was moved from this work item to 
2.  

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>

ACM Epic Done Checklist

See presentation and details.

Update with "Y" if Epic meets the requirement, "N" if it does not,  or "N/A" if not applicable.

• _ FIPS Readiness
• _ Works in Disconnected
• _ Global Proxy Support
• _ Installable to Infrastructure Nodes
• _ No impacts to Performance and Scalability
• _ Backup and Restorable