Epic Goal

ACM development and QE need and/or desire for many images that don't naturally live in the acm-d organization to be mirrored there.  This epic describes two primary use cases that are required.

Use cases:

1. Images from brew are required to be mirrored into acm-d since we do not want to point to brew as one of the locations we pull from.  (We could decide differently since we pull from brew for stage catalogs).  This currently applies to CAPI images.
2. We point to many images that are already delivered to registry.redhat.io.  We don't build these images, but some ACM teams need these images to exist in acm-d so simplify test/dev work.  Examples: RHEM, memcached, postgresql, configmap-reloader, etc

Why is this important?

It's important for dev/test scenarios to work well and to minimize complexity in how our installations need to be configured.  

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)