Uploaded image for project: 'OpenShift CFE'
  1. OpenShift CFE
  2. CFE-812

oc-mirror supports ImageTagMirrorSet and ImageDigestMirrorSet

    XMLWordPrintable

Details

    • Epic
    • Resolution: Done
    • Major
    • None
    • None
    • oc / oc-mirror, oc-mirror
    • None
    • IDMS/ITMS
    • False
    • None
    • False
    • Green
    • To Do
    • 0
    • 0% 0%
    • L
    • 0

    Description

      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

      Attachments

        Issue Links

          is depended on by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-160 ICSP migration to IDMS

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. 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

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-899 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 release images according to the requirements for enclave support

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OCPNODE-1258 ICSP Migration for OpenShift Components

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Spike - Represents a research-related task. CFE-817 Understand and evaluate work requested for IDMS

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              skhoury@redhat.com Sherine Khoury
              DanielMesser Daniel Messer
              Ramon Acedo Ramon Acedo
              Votes:
              6 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: