Goal: Deliver required tools, integrations, and processes for internal RH, certified ISVs, and OCP community operators to be created, validated/certified, and released for default availability on new OCP cluster deployments.

Benefit hypothesis: OCP ships with 3 default catalogs of content via OperatorHub (RH internal, ISV, community).  Content provided via this means should be functional and verified so that customers have a positive experience interacting with OperatorHub and OLM. 

Why is this important: A poor experience with an OperatorHub operator/application may lead to an overall negative view of OCP.  Continuously difficult or problematic pipeline adoption by workload operator teams may lead to them moving to an alternative form of delivery outside of operators, OLM and the central pipeline. 

Acceptance criteria:

• Ability to verify and certify workload operator content both statically and functionally on cluster
• Ability to promote content from preview/fast/stable channels
• Pipelines support operator metadata bundle and catalog index formats
• Pipelines able to backwork convert newly formatted operators to older nested directory/app registry format
• Pipelines are able to verify functionality on multiple OCP cluster versions and deployment infrastructures