-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
What is the nature and description of the request?
Using oc-mirror v2, I want the following workflow:
m2d:
pull release images into mirror_000000.tar
pull operator A,B,C images into mirror_000001.tar
pull operator D,F images into mirror_000002.tar
Now copy all archive files into the disconnected env.
d2m:
using a consolidated imageset config file (with release and all operators):
push all images to the mirror reg.
This does not work today and shows the following error:
error mirroring image docker://registry.redhat.io/redhat/redhat-operator-index:v4.19 error: initializing source docker://localhost:55000/redhat/redhat-operator-index:228003067d955dd79c300703560f5bbf: reading manifest 228003067d955dd79c300703560f5bbf in localhost:55000/redhat/redhat-operator-index: manifest unknown
Why does the customer need this? (List the business requirements here)
This simplifies the mirroring of images in "sets" or batches, e.g. :
Possible batches: ocp, odf, ocpv, ai, mesh3, sec, appdev ... etc
Once I have all the sets of operators, users can mix and match from a library of batches, and push the required sets of images into the mirror registry.
List any affected packages or components.
oc-mirror and OLM.