-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
oc-mirror v2: Add support for S3 as a source for archive files during d2m process
2. What is the nature and description of the request?
oc-mirror v2 currently supports uploading tar archive files or a directory of tar archives located on the same host where the oc mirror command is running. This RFE would enhance oc mirror to pull the tar archive files from an S3 bucket
3. Why does the customer need this? (List the business requirements here)
Many offline/disconnected customers use private commercial cloud regions with AWS, Azure, and Google. All of which have S3 services. The current process for d2m is to pull down the tar files to a bastion host and run the oc mirror d2m process. This RFE allows customers to keep the tar files in S3 and still use them to push into a private registry making the process smother and faster. This also reduces the risk that archive files will be lost when stored on a single bastion machine which may also fill up quickly. S3 storage is much cheaper than block storage tied to a cloud instance.
4. List any affected packages or components.
oc-mirror