As of 4.14 we will support the 'full architecture' mirroring of the catalog and 'multi' release image. This means that if a customer wants multi-arch compute for less than 4 of our architectures, they must still mirror content for architectures that they don't need. (ie. I'm running x86 and ppc64le, and I don't want s390x, and arm64)

The initial solution to this problem was to implement sparse manifest list mirroring outlined in these epics:
https://issues.redhat.com/browse/MIXEDARCH-204
https://issues.redhat.com/browse/MIXEDARCH-232
https://issues.redhat.com/browse/MIXEDARCH-224

Given that this effort won't be completed in the next few releases, we need to explore other options.

AC:

• Work with OTA, ART, the oc-mirror team(s)...etc to create a list of alternate methods of mirroring the ReleaseImage and Catalog content. No restrictions here, everything should be on the table. https://docs.google.com/document/d/1GMEXU_SJKPQCHvbjbQ4VHov_j1L2D-bpgYkdTljcQWg/edit

• Distill the above list of possibilities to a list of implementable solutions, with blockers and pros/cons.

• Determine if the list of implementable solutions is better/worse than Sparse Manifest solution (epics above). If so create an actionable steps (roadmap + epics) for the soonest possible release.