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

Improve user experience of oc-mirror with the OCI FBC feature

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • openshift-4.13
    • None
    • None
    • None
    • Improvement
    • 8
    • False
    • None
    • False
    • OCPSTRAT-173 - OC mirror enhancements
    • For OCI FBC feature, --oci-feature-action is not needed anymore. MirrorToMirror workflow is always implied (Partially disconnected workflow)
    • Enhancement
    • In Progress
    • CFE Sprint 231, CFE Sprint 232

      As IBM, I would like to use oc-mirror with the --use-oci-feature flag and ImageSetConfigs containing OCI-FBC operator catalogs to mirror these catalogs to a connected registry
      so that , regarding OCI FBC catalog:

      • all bundles specified in the ImageSetConfig and their related images are mirrored from their source registry to the destination registry
      • and the catalogs are mirrored from the local disk to the destination registry
      • and the ImageContentSourcePolicy and CatalogSource files are generated correctly

      and that regarding releases, additional images, helm charts:

      • The images that are selected for mirroring are mirrored to the destination registry using the MirrorToMirror workflow

      As an oc-mirror user I want a well documented and intuitive  process
      so that I can effectively and efficiently deliver image artifacts in both connected and disconnected installs with no impact on my current workflow

      Glossary:

      • OCI-FBC operator catalog: catalog image in oci format saved to disk, referenced with oci://path-to-image
      • registry based operator catalog: catalog image hosted on a container registry.

      References:

       

      Acceptance criteria:

      • No regression on oc-mirror use cases that are not using OCI-FBC feature
      • mirrorToMirror use case with oci feature flag should be successful when all operator catalogs in ImageSetConfig are OCI-FBC:
        • oc-mirror -c config.yaml docker://remote-registry --use-oci-feature succeeds
        • All release images, helm charts, additional images are mirrored to the remote-registry in an incremental manner (only new images are mirrored based on contents of the storageConfig)
        • All catalogs OCI-FBC, selected bundles and their related images are mirrored to the remote-registry and corresponding catalogSource and ImageSourceContentPolicy generated
        • All registry based catalogs, selected bundles and their related images are mirrored to the remote-registry and corresponding catalogSource and ImageSourceContentPolicy generated
      • mirrorToDisk use case with the oci feature flag is forbidden. The following command should fail:
        • oc-mirror --from=seq_xx_tar docker://remote-registry --use-oci-feature
      • diskToMirror use case with oci feature flag is forbidden. The following command should fail:

              skhoury@redhat.com Sherine Khoury
              skhoury@redhat.com Sherine Khoury
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: