Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

 ----- copied from RFE-3333 -----
1. Proposed title of this feature request

oc-mirror supports multi-arch filtering to decrease download time & data volume

2. What is the nature and description of the request?

oc-mirror should provide an option to let the user select the compute architectures they are targeting run in their disconnected environment. This allows them to save time and storage space to prepare and update the disconnected registry mirrors.

In particular oc-mirror should make use of the functionality described in PROJQUAY-3114 which is based on spec changes in OCI and Docker image specifications. oc-mirror should push manifest lists unchanged so that their digests do not differ from the source but should omit pushing child manifests which do not correspond to a list of desired compute architectures in the oc-mirror config file.

3. Why does the customer need this? (List the business requirements here)

Most customers in disconnected pay a premium for storage space. At the same time they are wasting storage space with the current implementation of oc-mirror because it has to mirror all manifest list (multi-arch) images including all child manifests / images which significantly increases the storage consumption. They very often only have a single compute architecture but have to account for storage space for all of OCPs supported compute architectures.
Only storing the images that correspond to the actually required compute architectures the customers have will significantly reduce the amount of registry mirror storage and download time required to main disconnected copies of OCP core payload and optional operator images.
4. List any affected packages or components.
 ------------------------------------------------------

<your text here>

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

<your text here>

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

 This Feature was generated in OCPSTRAT via acceptance of RFE-3333. Ensure the stated Acceptance Criteria below will fulfill the needs specified in the RFE.

<enter general Feature acceptance here>

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>