Uploaded image for project: 'Multiple Architecture Enablement'
  1. Multiple Architecture Enablement
  2. MULTIARCH-4247

Define Path forward for sparse manifest work.

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • MA-Compute Dev
    • False
    • None
    • False
    • NEW
    • Multi-Arch Sprint 250

      We currently have several epics wrt mirroring the release payload and container catalog. 
      Need to sync with the oc mirror and image registry teams and clearly define outcomes, timelines and a path forward.

      Mirroring w/sparse manifest support: 

      https://issues.redhat.com/browse/MIXEDARCH-204 support sparse manifest list in "oc-mirror"
      https://issues.redhat.com/browse/MIXEDARCH-232 support sparse manifest list in the quay registry
      https://issues.redhat.com/browse/MIXEDARCH-224 support sparse manifest list in the "oc" command (done?)

            jeffdyoung Jeff Young
            jeffdyoung Jeff Young
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: