Changes from oc-mirror plugin v1 to v2

Before migrating from oc-mirror plugin v1 to v2, you must review the updated mirroring workflow commands, which have changed to align with the new v2 workflow.

  • For mirror-to-disk, run the following command:

    $ oc-mirror --config isc.yaml file://<directory_name> --v2

  • For disk-to-mirror, run the following command:

    $ oc-mirror --config isc.yaml --from file://<directory_name> docker://<remote_registry> --v2

  • For mirror-to-mirror, run the following command:

    $ oc-mirror --config isc.yaml --workspace file://<directory_name> docker://<remote_registry> --v2
    Note

    --workspace is now required for mirror-to-mirror operation.

    • API version update: The ImageSetConfiguration API version changes from v1alpha2 (v1) to v2alpha1 (v2). You must manually update the configuration files before migration.

    • Configuration changes:

      • storageConfig must be removed in oc-mirror plugin v2.

      • Incremental mirroring is now handled automatically through the working directory or local cache.

    • Changes in results directory: All custom resources to be applied to the disconnected cluster are generated in the <workspace_path>/working-dir/cluster-resources directory after the migration.

      • Outputs in oc-mirror plugin v2 are not stored in the same location as oc-mirror plugin v1.

      • You must check the cluster-resources folder under the working directory for the following resources:

  • ImageDigestMirrorSet (IDMS)

  • ImageTagMirrorSet (ITMS)

  • CatalogSource

  • ClusterCatalog

  • UpdateService

    • Workspace and directory naming: Follow the new oc-mirror v2 convention to prevent any potential data inconsistencies when transitioning between versions.

      • The oc-mirror plugin v1 oc-mirror-workspace directory is no longer needed.

      • Use a new directory for oc-mirror plugin v2 to avoid conflicts.

    • Replacing ImageContentSourcePolicy (ICSP) resources with IDMS/ITMS:

      Important

      Deleting all ImageContentSourcePolicy (ICSP) resources might remove configurations unrelated to oc-mirror.

      To avoid unintended deletions, identify ICSP resources generated by oc-mirror before removing them. If you are unsure, check with your cluster administrator. For more information, see "Mirroring images for a disconnected installation by using the oc-mirror plugin v2".

      • In oc-mirror plugin v2, the ICSP resource is replaced by ImageDigestMirrorSet (IDMS) and ImageTagMirrorSet (ITMS) resources.

← Previous: Mirroring Operator catalogs for use with disconnected clusters | ↑ Up: Disconnected environments | ⌂ Home: Red Hat OpenShift Container Platform | Next: Migrating to oc-mirror plugin v2 →