installing-mtc-restricted.adoc

Installing the Migration Toolkit for Containers in a restricted network environment

You can install the {mtc-full} ({mtc-short}) on {product-title} 4 in a restricted network environment by performing the following procedures:

1. Create a mirrored Operator catalog.

   This process creates a mapping.txt file, which contains the mapping between the registry.redhat.io image and your mirror registry image. The mapping.txt file is required for installing the legacy {mtc-full} Operator on an {product-title} 4.2 to 4.5 source cluster.

2. Install the {mtc-full} Operator on the {product-title} {product-version} target cluster by using Operator Lifecycle Manager.

   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 remote cluster.

3. Install the {mtc-full} Operator on the source cluster:

   • {product-title} 4.6 or later: Install the {mtc-full} Operator by using Operator Lifecycle Manager.

   • {product-title} 4.2 to 4.5: Install the legacy {mtc-full} Operator from the command line interface.

4. Configure object storage to use as a replication repository.

Note	To install {mtc-short} on {product-title} 3, see Installing the legacy {mtc-full} Operator on {product-title} 3.

To uninstall {mtc-short}, see Uninstalling {mtc-short} and deleting resources.

modules/migration-compatibility-guidelines.adoc modules/migration-installing-mtc-on-ocp-4.adoc modules/migration-installing-legacy-operator.adoc modules/migration-about-configuring-proxies.adoc modules/migration-configuring-proxies.adoc

For more information, see Configuring the cluster-wide proxy.

Configuring a replication repository

The Multicloud Object Gateway is the only supported option for a restricted network environment.

{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.

Prerequisites

• 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-configuring-mcg.adoc

Additional resources

• Disconnected environment in the {rh-storage-first} documentation.

• {mtc-short} workflow

• About data copy methods

• Adding a replication repository to the {mtc-short} web console

modules/migration-uninstalling-mtc-clean-up.adoc