Closed djzager closed 2 years ago
/kind feature /priority critical /triage accepted
This issue synced with: https://issues.redhat.com/browse/MTRHO-113
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.
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:
crane-export
targeting source cluster, we must have the manifestsoc-registry-info
targeting source and destination clusterscrane-skopeo-sync-gen
using the emitted results fromoc registry info
and the export results stored in the common workspaceskopeo-sync
targeting destination clusterDependent 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
whenoc registry info
doesn't get us what we want.