Feature Overview (aka. Goal Summary)  

The ability to us OpenShift in dIsconnected mode is critical in security conscious environments, part of making this experience as smooth as possible is the ability to use oc mirror. This feature is to track bringing feature   

Goals (aka. expected user outcomes)

The experience of using oc mirror on OpenShift on Arm will be akin to the current day experience of using it on x86 architectures.

Requirements (aka. Acceptance Criteria):

oc mirror to work as expected on OpenShift on Arm.

Use Cases (Optional):

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

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.

Out of Scope

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

Background

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

Customer Considerations

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

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects 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.