Uploaded image for project: 'Cluster Integration and Delivery'
  1. Cluster Integration and Delivery
  2. CLID-46 Retro compatibility operator mirroring
  3. CLID-49

As a developer I want to ensure that the current cache is updated with the latest manifest

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-876 - [Tech Preview] OC mirror multiple internet disconnected enclaves
    • ---
    • ---
    • CLID Sprint 252

      During the collector phase it is needed to check if the manifest of the operator catalog and release in the remote mirror registry is the same as the one currently in the cache, if it is not download all the latest content and add it to the cache.

      Acceptance criteria:

      • I should be able to mirror from 2 catalogs without the content of working-dir/operator-images/redhat-operator-index or working-dir/hold-operator/redhat-operator-index of 1 catalog replacing the other (already covered AFAIK)
        mirror: 
          operators: 
          - catalog: redhat-operator-index:v4.12
          - catalog: redhat-operator-index:v4.13
        
      • In the event of z-stream release of v4.12, I want oc-mirror to detect there is a new image to pull from registry, and not rely on the existance of folder working-dir/operator-images/redhat-operator-index/v4.12 or working-dir/hold-operator/redhat-operator-index/v4.12 as a reason not to get the fresh digest for this tag
        mirror: 
          operators: 
          - catalog: redhat-operator-index:v4.12
        

              rh-ee-aguidi Alex Guidi
              luzuccar@redhat.com Luigi Mario Zuccarelli
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: