You can install the {mtc-full} ({mtc-short}) on {product-title} 3 and 4.
After you install the {mtc-full} Operator on {product-title} {product-version} by using the Operator Lifecycle Manager, you manually install the legacy {mtc-full} Operator on {product-title} 3.
By default, the {mtc-short} web console and the Migration Controller pod run on the target cluster. You can configure the Migration Controller custom resource manifest to run the {mtc-short} web console and the Migration Controller pod on a source cluster or on a remote cluster.
After you have installed {mtc-short}, you must configure an object storage to use as a replication repository.
To uninstall {mtc-short}, see Uninstalling {mtc-short} and deleting resources.
modules/migration-compatibility-guidelines.adoc modules/migration-installing-legacy-operator.adoc modules/migration-installing-mtc-on-ocp-4.adoc modules/migration-about-configuring-proxies.adoc modules/migration-configuring-proxies.adoc
For more information, see Configuring the cluster-wide proxy.
You must configure an object storage to use as a replication repository. The {mtc-full} ({mtc-short}) copies data from the source cluster to the replication repository, and then from the replication repository to the target cluster.
{mtc-short} supports the file system and snapshot data copy methods for migrating data from the source cluster to the target cluster. You can select a method that is suited for your environment and is supported by your storage provider.
The following storage providers are supported:
-
Generic S3 object storage, for example, Minio or Ceph S3
-
All clusters must have uninterrupted network access to the replication repository.
-
If you use a proxy server with an internally hosted replication repository, you must ensure that the proxy allows access to the replication repository.
modules/migration-uninstalling-mtc-clean-up.adoc :installing-3-4!: