migtools / crane-ui-plugin

OpenShift Dynamic Plugin for Crane UI
1 stars 11 forks source link

[RFE] Generate new pipeline for handling image transfer #110

Closed djzager closed 2 years ago

djzager commented 2 years ago

Relevant Slack conversation.

In the import wizard, we need to recognize when a source for import includes ImageStreams. If ImageStreams are found we ask the user if they wish to migrate them (future iterations may determine this for the user). The resulting pipeline should look something like:

  1. crane-export targeting source cluster, we must have the manifests
  2. oc-registry-info targeting source and destination clusters
  3. crane-skopeo-sync-gen using the emitted results from oc registry info and the export results stored in the common workspace
  4. skopeo-sync targeting destination cluster

Dependent issues include:

Updates based on Shawn's comment https://github.com/konveyor/enhancements/pull/77/files#r922514703 that made me realize we could fallback to oc get route when oc registry info doesn't get us what we want.

djzager commented 2 years ago

/kind feature /priority critical /triage accepted

github-actions[bot] commented 2 years ago

This issue synced with: https://issues.redhat.com/browse/MTRHO-113

djzager commented 2 years ago

https://github.com/konveyor/enhancements/pull/77

djzager commented 2 years ago

The problem with creating a whole new pipeline is that it opens the door to what we should allow with respect to source/destination registry configurations (ie. would we support quay registries or in cluster quay?).

For the sake of tech-preview we are descoping the new pipeline in favor of simply including the image-sync task in the Cutover pipeline. This will support the transfer of images as necessary.