mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
42db5812e2
Ingress and load balancing Advanced networking configuring network settings networking overview Ingress and load balancing Advanced networking configuring network settings
58 lines
3.9 KiB
Plaintext
58 lines
3.9 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="installing-restricted-3-4"]
|
|
= Installing the Migration Toolkit for Containers in a restricted network environment
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: installing-restricted-3-4
|
|
:installing-restricted-3-4:
|
|
|
|
toc::[]
|
|
|
|
You can install the {mtc-full} ({mtc-short}) on {product-title} 3 and 4 in a restricted network environment by performing the following procedures:
|
|
|
|
. Create a xref:../disconnected/using-olm.adoc#olm-mirror-catalog_olm-restricted-networks[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 Operator on the source cluster.
|
|
. 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 link:https://access.redhat.com/articles/5064151[source cluster or on a remote cluster].
|
|
|
|
. Install the _legacy_ {mtc-full} Operator on the {product-title} 3 source cluster from the command-line interface.
|
|
. Configure object storage to use as a replication repository.
|
|
|
|
To uninstall {mtc-short}, see xref:../migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc#migration-uninstalling-mtc-clean-up_installing-restricted-3-4[Uninstalling {mtc-short} and deleting resources].
|
|
|
|
include::modules/migration-compatibility-guidelines-3-to-4.adoc[leveloffset=+1]
|
|
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
|
|
include::modules/migration-installing-legacy-operator.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
|
|
|
|
The Multicloud Object Gateway is the only supported option for a restricted network environment.
|
|
|
|
{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.
|
|
|
|
[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]
|
|
|
|
[role="_additional-resources"]
|
|
[id="{context}_configuring-replication-repository-additional-resources"]
|
|
=== Additional resources
|
|
|
|
* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.9/html/planning_your_deployment/disconnected-environment_rhodf[Disconnected environment] in the {rh-storage-first} documentation.
|
|
* 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-restricted-3-4!:
|