9/28/21 Update:

ART is only focusing on core OCP payloads now- our best course of action here is to onboard OMR to CPaaS and put together a separate build/release pipeline so that OMR can be released with it's own Advisory.  We can build a container image but instead of publishing to Container Catalog, the builds should be released through a TBD process which will publish the resulting binary to the mirror downloads page (see below).

Immediate deliverable here is to onboard OMR to CPaaS and get builds working.

--------------------------------------

We need to work with ART on building/signing the binary so that it can be hosted on the mirrors page for download (the AIO will NOT be downloaded as a container image).

Steps on how this is done (from Justin Pierce, ART):

1. ART builds a set of CVO operators in OSBS. The installer, and other binaries, are built during this process during the multi-stage image builds.
2. ART then assembles a release payload from the CVO operator images.
3. oc adm release extract is run against this release payloads to extract the binaries. ART runs this as part of their release pipelines and publishes the artifacts out to the openshift mirrors; pre-ga location (OCP 4.7 at present) . post-ga location.
4. During the publish to the mirror, an signature is generated for the files we are publishing using Red Hat signing keys (see sha256sum.* in this example directory). This signature is also sent to the mirror so that the binaries can be verified by consumers.
5. The cloud.redhat.com team knows about these locations and hyperlinks to various locations within the mirrored locations.

Task is to raise a Jira on ART's board (https://issues.redhat.com/secure/RapidBoard.jspa?rapidView=5334) with details on how to find the binary and extract.