-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
IDMS/ITMS
-
False
-
None
-
False
-
Green
-
To Do
-
L
Story: As a user of oc-mirror I can make use of the fact that OpenShift now supports tag-based mirror references so that I can mirror and use content in disconnected environments that is referred to by image tags rather than digest.
Background: RFE-1608 has been implemented and will ship with OpenShift 4.13. This will introduce new APIs to control image pull redirection for mirrored content. More details in the release notes preview: https://docs.openshift.com/container-platform/4.13/release_notes/ocp-4-13-release-notes.html#ocp-4-13-nodes-mirror
Acceptance criteria:
- custom images, helm charts and operator catalogs with tag-based image references can be mirrored by oc-mirror as well, in turn producing a ImageTagMirrorSet manifest
- custom images, helm charts, operator catalogs and OCP payload with digest-based references should still produce an ImageDigestMirrorSet after mirroring
- the behavior to produce ImageTagMirrorSet should be opt-in and controllable at the level of the ImageSetConfig API since older OCP clusters may not support this new API
- when attempting to mirror content that is referenced by tags and the above option is not set, the mirror operation should fail with a human-readable error message
- the behavior to produce ImageDigestMirror manifests instead of ImageContentSourcePolicy should be opt-in and controllable at the level of the ImageSetConfig API since older OCP clusters may not support this new API
- is depended on by
-
OCPSTRAT-160 ICSP migration to IDMS
-
- Closed
-
- is related to
-
CLID-10 As a user I want to be able to use oc-mirror in both partial and fully disconnected install scenarios so that I can generate relevant metadata useful for validation and implementation for catalog images according to the requirements for enclave support
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
CFE-817 Understand and evaluate work requested for IDMS
-
- Closed
-
