MTC tool to migrate OCP 4.x to ROSA 4.x

Resolution

• Can I use the MTC tool to migrate OCP 4.6 to ROSA 4.7.16?

Yes, but you will need cluster-admin granted on the ROSA cluster.

• Can this tool migrate the Operator based apps like Quay and 3-scale into ROSA 4.7.16?

There will be complications migrating Operator based applications. MTC may be able to help, but this would likely need manual interventions. It will be good if you try in DEV and find the workflow and problems in regard to migration Operator based applications so we can suggest and fix one by one.

• What are the limitations of this tool?

Requirement of cluster-admin and network connectivity between Source/Target clusters along with access to a shared Object Storage location. We are lacking in our support for handling Operator enabled applications.

• From the MTC document it seems we only support OCP 3.x --> OCP 4.7.

  "AWS, Google Cloud Provider, and Microsoft Azure support the snapshot copy method."

No, MTC can support anything from OCP 3.7+, migrating OCP 4 to OCP 4 is fine.

• Can customers perform a "snapshot copy'' method from OCP 4.x to ROSA 4.7 successfully?

In general this will require that an EBS snapshot created on the OCP 4.x cluster is visible and usable by the ROSA cluster. If the AWS requirements are met, it is expected this to function.

• Can this tool migrate the Operator based apps like Quay and 3-scale?

3-Scale has its own backup and migration methods. So we cant confirm that yet. We need to check further with 3scale team if that is feasible with MTC. Related to Quay, it is not possible, but maybe only the operator which could be simpler to set it and connect to the external registry.