Uploaded image for project: 'Cluster Integration and Delivery'
  1. Cluster Integration and Delivery
  2. CLID-290

As a user I would like to filter the images based on the CPU architecture

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • oc-mirror
    • Sparse Manifest
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-1808 - oc-mirror v2: Multi-arch filtering via Sparse Manifests
    • OCPSTRAT-1808oc-mirror v2: Multi-arch filtering via Sparse Manifests
    • 100% To Do, 0% In Progress, 0% Done
    • ---
    • ---

      Possible Solution:

      • Solution 1: copy the manifest list as it is with its signature (cosign tag-based).

                     Requirement 1: To test this solution it is necessary a registry which supports sparse manifest (does not verify if all the images on the manifest list are present). Also with this solution the customer should use a supported registry.
                     Requirement 2: OCPSTRAT-1869 / CLID-289 needs to be done

       

      Open Questions:

      • Level of the signature

                 Question 1: Is the signature in the higher level (manifest list) or is it on the manifest level (image level) ? 

      Dependencies

       

              Unassigned Unassigned
              rh-ee-aguidi Alex Guidi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: