mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
64 lines
4.1 KiB
Plaintext
64 lines
4.1 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="installing-3-4"]
|
|
= Installing the Migration Toolkit for Containers
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: installing-3-4
|
|
:installing-3-4:
|
|
|
|
toc::[]
|
|
|
|
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 link:https://access.redhat.com/articles/5064151[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 xref:../migrating_from_ocp_3_to_4/installing-3-4.adoc#migration-uninstalling-mtc-clean-up_installing-3-4[Uninstalling {mtc-short} and deleting resources].
|
|
|
|
include::modules/migration-compatibility-guidelines-3-to-4.adoc[leveloffset=+1]
|
|
include::modules/migration-installing-legacy-operator.adoc[leveloffset=+1]
|
|
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
|
|
include::modules/migration-about-configuring-proxies.adoc[leveloffset=+1]
|
|
include::modules/migration-configuring-proxies.adoc[leveloffset=+2]
|
|
|
|
For more information, see xref:../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
|
|
|
|
[id="configuring-replication-repository_{context}"]
|
|
== Configuring a replication repository
|
|
|
|
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 xref:../migrating_from_ocp_3_to_4/about-mtc-3-4.adoc#migration-understanding-data-copy-methods_about-mtc-3-4[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:
|
|
|
|
* xref:../migrating_from_ocp_3_to_4/installing-3-4.adoc#migration-configuring-mcg_installing-3-4[Multicloud Object Gateway]
|
|
* xref:../migrating_from_ocp_3_to_4/installing-3-4.adoc#migration-configuring-aws-s3_installing-3-4[Amazon Web Services S3]
|
|
* xref:../migrating_from_ocp_3_to_4/installing-3-4.adoc#migration-configuring-gcp_installing-3-4[{gcp-full}]
|
|
* xref:../migrating_from_ocp_3_to_4/installing-3-4.adoc#migration-configuring-azure_installing-3-4[Microsoft Azure Blob]
|
|
* Generic S3 object storage, for example, Minio or Ceph S3
|
|
|
|
[id="replication-repository-prerequisites_{context}"]
|
|
=== 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.
|
|
|
|
include::modules/migration-configuring-mcg.adoc[leveloffset=+2]
|
|
include::modules/migration-configuring-aws-s3.adoc[leveloffset=+2]
|
|
include::modules/migration-configuring-gcp.adoc[leveloffset=+2]
|
|
include::modules/migration-configuring-azure.adoc[leveloffset=+2]
|
|
|
|
[role="_additional-resources"]
|
|
[id="{context}_configuring-replication-repository-additional-resources"]
|
|
=== Additional resources
|
|
|
|
* xref:../migrating_from_ocp_3_to_4/about-mtc-3-4.adoc#migration-mtc-workflow_about-mtc-3-4[{mtc-short} workflow]
|
|
* xref:../migrating_from_ocp_3_to_4/about-mtc-3-4.adoc#migration-understanding-data-copy-methods_about-mtc-3-4[About data copy methods]
|
|
* xref:../migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc#migration-adding-replication-repository-to-cam_migrating-applications-3-4[Adding a replication repository to the {mtc-short} web console]
|
|
|
|
include::modules/migration-uninstalling-mtc-clean-up.adoc[leveloffset=+1]
|
|
:installing-3-4!:
|