openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

[enterprise-4.8] BZ1962111: Reorganize MTC

Browse Source
This commit is contained in:
Samantha Gidlow
2021-06-02 10:45:29 -04:00
committed by Avital Pinnick
parent 72f9416183
commit a3c22beecf
67 changed files with 203 additions and 598 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
_topic_map.yml
View File

@@ -1972,35 +1972,21 @@ Topics:
File: troubleshooting-3-4
---
Name: Migration Toolkit for Containers
Dir: migration
Dir: migration-toolkit-for-containers
Distros: openshift-enterprise,openshift-origin
Topics:
- Name: Migrating from OpenShift Container Platform 4.1
Dir: migrating_4_1_4
Topics:
- Name: About the Migration Toolkit for Containers
File: migrating-application-workloads-4-1-4
- Name: Installing and upgrading the Migration Toolkit for Containers
File: deploying-cam-4-1-4
- Name: Configuring object storage for a replication repository
File: configuring-replication-repository-4-1-4
- Name: Migrating your applications
File: migrating-applications-with-cam-4-1-4
- Name: Troubleshooting
File: troubleshooting-4-1-4
- Name: Migrating from OpenShift Container Platform 4.2 and later
Dir: migrating_4_2_4
Topics:
- Name: About the Migration Toolkit for Containers
File: migrating-application-workloads-4-2-4
- Name: Installing and upgrading the Migration Toolkit for Containers
File: deploying-cam-4-2-4
- Name: Configuring object storage for a replication repository
File: configuring-replication-repository-4-2-4
- Name: Migrating your applications
File: migrating-applications-with-cam-4-2-4
- Name: Troubleshooting
File: troubleshooting-4-2-4
- Name: About MTC
File: about-mtc
- Name: Installing MTC
File: installing-mtc
- Name: Installing MTC in a restricted network environment
File: installing-mtc-restricted
- Name: Upgrading MTC
File: upgrading-mtc
- Name: Migrating your applications
File: migrating-applications-with-mtc
- Name: Troubleshooting
File: troubleshooting-mtc
---
Name: API reference
Dir: rest_api

30
migrating_from_ocp_3_to_4/configuring-replication-repository-3-4.adoc
View File

@@ -1,30 +0,0 @@
[id="configuring-replication-repository-3-4"]
= Configuring object storage for a replication repository
include::modules/common-attributes.adoc[]
:context: configuring-replication-repository-3-4
toc::[]
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/configuring-replication-repository-3-4.adoc#migration-configuring-mcg_configuring-replication-repository-3-4[Multi-Cloud Object Gateway (MCG)]
* xref:../migrating_from_ocp_3_to_4/configuring-replication-repository-3-4.adoc#migration-configuring-aws-s3_configuring-replication-repository-3-4[Amazon Web Services (AWS) S3]
* xref:../migrating_from_ocp_3_to_4/configuring-replication-repository-3-4.adoc#migration-configuring-gcp_configuring-replication-repository-3-4[Google Cloud Provider (GCP)]
* xref:../migrating_from_ocp_3_to_4/configuring-replication-repository-3-4.adoc#migration-configuring-azure_configuring-replication-repository-3-4[Microsoft Azure]
* Generic S3 object storage, for example, Minio or Ceph S3
In a restricted environment, you can create an internally hosted replication repository.
.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=+1]
include::modules/migration-configuring-aws-s3.adoc[leveloffset=+1]
include::modules/migration-configuring-gcp.adoc[leveloffset=+1]
include::modules/migration-configuring-azure.adoc[leveloffset=+1]

2
migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc
View File

@@ -17,8 +17,6 @@ By default, the {mtc-short} web console and the `Migration Controller` pod run o
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].
You must create an Operator catalog from a mirror image in a local registry. See xref:../operators/admin/olm-restricted-networks.adoc[Using Operator Lifecycle Manager on restricted networks] for instructions.
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
include::modules/migration-installing-mtc-on-ocp-3.adoc[leveloffset=+1]

2
migrating_from_ocp_3_to_4/upgrading-3-4.adoc
View File

@@ -11,7 +11,7 @@ You can upgrade the {mtc-full} ({mtc-short}) by using the {product-title} web co
====
You must ensure that you upgrade to the same {mtc-short} version on all clusters.
If you are upgrading {mtc-short} version 1.3, you must perform an additional procedure to update the `MigPlan` custom resource (CR).
If you are upgrading from {mtc-short} version 1.3, you must perform an additional procedure to update the `MigPlan` custom resource (CR).
====
include::modules/migration-upgrading-mtc-on-ocp-4.adoc[leveloffset=+1]

19
migration-toolkit-for-containers/about-mtc.adoc Normal file
View File

@@ -0,0 +1,19 @@
[id="about-mtc"]
= About the {mtc-full}
include::modules/common-attributes.adoc[]
:context: about-mtc
toc::[]
The {mtc-full} ({mtc-short}) web console and API, based on Kubernetes custom resources, enable you to migrate stateful application workloads at the granularity of a namespace.
The {mtc-short} console is installed on the target cluster by default. You can configure the {mtc-full} Operator to install the console on a link:https://access.redhat.com/articles/5064151[remote 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.
You can use migration hooks to run Ansible playbooks at certain points during the migration. The hooks are added when you create a migration plan.
include::modules/migration-mtc-workflow.adoc[leveloffset=+1]
include::modules/migration-mtc-custom-resources.adoc[leveloffset=+1]
include::modules/migration-understanding-data-copy-methods.adoc[leveloffset=+1]
include::modules/migration-about-migration-hooks.adoc[leveloffset=+1]

1
migration-toolkit-for-containers/images Symbolic link
View File

@@ -0,0 +1 @@
../images

34
migration-toolkit-for-containers/installing-mtc-restricted.adoc Normal file
View File

@@ -0,0 +1,34 @@
[id="installing-mtc-restricted"]
= Installing the Migration Toolkit for Containers in a restricted network environment
include::modules/common-attributes.adoc[]
:context: installing-mtc-restricted
:installing-mtc-restricted:
toc::[]
You can install the {mtc-full} ({mtc-short}) on {product-title} 4 in a restricted network environment.
[IMPORTANT]
====
You must install the same {mtc-short} version on all clusters.
====
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[remote cluster].
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
[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. Multi-Cloud Object Gateway (MCG) is the only supported option for a restricted network environment.
{mtc-short} supports the xref:../migration-toolkit-for-containers/about-mtc.adoc#migration-understanding-data-copy-methods_about-mtc[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.
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]
:installing-mtc-restricted!:

44
migration-toolkit-for-containers/installing-mtc.adoc Normal file
View File

@@ -0,0 +1,44 @@
[id="installing-mtc"]
= Installing the Migration Toolkit for Containers
include::modules/common-attributes.adoc[]
:context: installing-mtc
:installing-mtc:
toc::[]
You can install the {mtc-full} ({mtc-short}) on {product-title} 4.
[IMPORTANT]
====
You must install the same {mtc-short} version on all clusters.
====
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[remote cluster].
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
[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:../migration-toolkit-for-containers/about-mtc.adoc#migration-understanding-data-copy-methods_about-mtc[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.
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.
The following storage providers are supported:
* Multi-Cloud Object Gateway (MCG)
* Amazon Web Services (AWS) S3
* Google Cloud Provider (GCP)
* Microsoft Azure Blob
* Generic S3 object storage, for example, Minio or Ceph S3
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]
:installing-mtc!:

27
migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc → migration-toolkit-for-containers/migrating-applications-with-mtc.adoc
View File

@@ -1,14 +1,14 @@
[id="migrating-applications-with-cam-4-2-4"]
[id="migrating-applications-with-mtc_{context}"]
= Migrating your applications
include::modules/common-attributes.adoc[]
:context: migrating-4-2-4
:migrating-4-2-4:
:context: migrating-applications-with-mtc
toc::[]
You can migrate your applications by using the {mtc-full} ({mtc-short}) web console or on the command line.
You can migrate your applications by using the {mtc-full} ({mtc-short}) web console or from the command line.
include::modules/migration-prerequisites.adoc[leveloffset=+1]
include::modules/migration-updating-deprecated-internal-images.adoc[leveloffset=+2]
include::modules/migration-creating-ca-bundle.adoc[leveloffset=+2]
include::modules/migration-configuring-proxy-for-dvm.adoc[leveloffset=+2]
include::modules/migration-writing-ansible-playbook-hook.adoc[leveloffset=+2]
@@ -16,9 +16,9 @@ include::modules/migration-writing-ansible-playbook-hook.adoc[leveloffset=+2]
[id="migrating-applications-additional-resources_{context}"]
=== Additional resources
* xref:../../migration/migrating_4_2_4/migrating-application-workloads-4-2-4.adoc#migration-about-migration-hooks_migrating-4-2-4[About migration hooks]
* xref:../../migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc#mighook_migrating-4-2-4[MigHook custom resource]
* xref:../../migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc#migplan_migrating-4-2-4[MigPlan custom resource]
* xref:../migration-toolkit-for-containers/about-mtc.adoc#migration-about-migration-hooks_about-mtc[About migration hooks]
* xref:../migration-toolkit-for-containers/migrating-applications-with-mtc.adoc#mighook_migrating-applications-with-mtc[MigHook custom resource]
* xref:../migration-toolkit-for-containers/migrating-applications-with-mtc#migplan_migrating-applications-with-mtc[MigPlan custom resource]
[id="migrating-applications-mtc-web-console_{context}"]
== Migrating your applications by using the {mtc-short} web console
@@ -34,7 +34,7 @@ include::modules/migration-running-migration-plan-cam.adoc[leveloffset=+2]
[id="migrating-applications-mtc-cli_{context}"]
== Migrating your applications from the command line
You can migrate your applications on the command line by using the {mtc-short} custom resources (CRs).
You can migrate your applications on the command line by creating or editing the {mtc-short} custom resource (CR) manifests.
You can migrate applications from a local cluster to a remote cluster, from a remote cluster to a local cluster, and between remote clusters.
@@ -60,11 +60,12 @@ include::modules/migration-migrating-applications-api.adoc[leveloffset=+2]
include::modules/migration-mtc-cr-manifests.adoc[leveloffset=+2]
[id="migrating-applications-mtc-cli-additional-resources_{context}"]
=== Additional resources
== Additional resources
* xref:../../migration/migrating_4_2_4/migrating-application-workloads-4-2-4.adoc#migration-about-migration-hooks_migrating-4-2-4[About migration hooks]
* xref:../../migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc#mighook_migrating-4-2-4[MigHook custom resource]
* xref:../../migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc#migplan_migrating-4-2-4[MigPlan custom resource]
* xref:../registry/securing-exposing-registry.adoc#registry-exposing-secure-registry-manually_securing-exposing-registry[Exposing a secure registry manually]
* xref:../migration-toolkit-for-containers/about-mtc.adoc#file-system-copy-method_about-mtc[{mtc-short} file system copy method]
* xref:../migration-toolkit-for-containers/about-mtc.adoc#snapshot-copy-method_about-mtc[{mtc-short} snapshot copy method]
* xref:../migration-toolkit-for-containers/troubleshooting-mtc.adoc#migration-viewing-migration-crs_troubleshooting-mtc[Viewing migration custom resources]
[id="configuring-migration-plan_{context}"]
== Configuring a migration plan
@@ -73,5 +74,3 @@ You can increase the number of objects to be migrated or exclude resources from
include::modules/migration-changing-migration-plan-limits.adoc[leveloffset=+2]
include::modules/migration-excluding-resources.adoc[leveloffset=+2]
:!migrating-4-2-4:

1
migration-toolkit-for-containers/modules Symbolic link
View File

@@ -0,0 +1 @@
../modules

11
migration/migrating_4_2_4/troubleshooting-4-2-4.adoc → migration-toolkit-for-containers/troubleshooting-mtc.adoc
View File

@@ -1,8 +1,7 @@
[id="troubleshooting-4-2-4"]
[id="troubleshooting-mtc"]
= Troubleshooting
include::modules/common-attributes.adoc[]
:context: migrating-4-2-4
:migrating-4-2-4:
:context: troubleshooting-mtc
toc::[]
@@ -38,7 +37,5 @@ include::modules/migration-known-issues.adoc[leveloffset=+1]
[id="troubleshooting-additional-resources_{context}"]
== Additional resources
* xref:../../migration/migrating_4_2_4/migrating-application-workloads-4-2-4.adoc#migration-mtc-workflow_migrating-4-2-4[{mtc-short} workflow]
* xref:../../migration/migrating_4_2_4/migrating-application-workloads-4-2-4.adoc#migration-mtc-custom-resources_migrating-4-2-4[{mtc-short} custom resources]
:!migrating-4-2-4:
* xref:../migration-toolkit-for-containers/about-mtc.adoc#migration-mtc-workflow_about-mtc[{mtc-short} workflow]
* xref:../migration-toolkit-for-containers/about-mtc.adoc#migration-mtc-custom-resources_about-mtc[{mtc-short} custom resources]

19
migration-toolkit-for-containers/upgrading-mtc.adoc Normal file
View File

@@ -0,0 +1,19 @@
[id="upgrading-3-4"]
= Upgrading the Migration Toolkit for Containers
include::modules/common-attributes.adoc[]
:context: upgrading-3-4
toc::[]
You can upgrade the {mtc-full} ({mtc-short}) by using the {product-title} web console.
[IMPORTANT]
====
You must ensure that you upgrade to the same {mtc-short} version on all clusters.
If you are upgrading from {mtc-short} version 1.3, you must perform an additional procedure to update the `MigPlan` custom resource (CR).
====
include::modules/migration-upgrading-mtc-on-ocp-4.adoc[leveloffset=+1]
include::modules/migration-upgrading-mtc-on-ocp-3.adoc[leveloffset=+1]
include::modules/migration-upgrading-from-mtc-1-3.adoc[leveloffset=+1]

33
migration/migrating_4_1_4/configuring-replication-repository-4-1-4.adoc
View File

@@ -1,33 +0,0 @@
[id="configuring-replication-repository-4-1-4"]
= Configuring object storage for a replication repository
include::modules/common-attributes.adoc[]
:context: migrating-4-1-4
:migrating-4-1-4:
toc::[]
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:../../migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc#migration-understanding-data-copy-methods_migrating-4-1-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:../../migration/migrating_4_1_4/configuring-replication-repository-4-1-4.adoc#migration-configuring-mcg_migrating-4-1-4[Multi-Cloud Object Gateway (MCG)]
* xref:../../migration/migrating_4_1_4/configuring-replication-repository-4-1-4.adoc#migration-configuring-aws-s3_migrating-4-1-4[Amazon Web Services (AWS) S3]
* xref:../../migration/migrating_4_1_4/configuring-replication-repository-4-1-4.adoc#migration-configuring-gcp_migrating-4-1-4[Google Cloud Provider (GCP)]
* xref:../../migration/migrating_4_1_4/configuring-replication-repository-4-1-4.adoc#migration-configuring-azure_migrating-4-1-4[Microsoft Azure]
* Generic S3 object storage, for example, Minio or Ceph S3
In a restricted environment, you can create an internally hosted replication repository.
.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=+1]
include::modules/migration-configuring-aws-s3.adoc[leveloffset=+1]
include::modules/migration-configuring-gcp.adoc[leveloffset=+1]
include::modules/migration-configuring-azure.adoc[leveloffset=+1]
:!migrating-4-1-4:

84
migration/migrating_4_1_4/deploying-cam-4-1-4.adoc
View File

@@ -1,84 +0,0 @@
[id="deploying-cam-4-1-4"]
= Installing and upgrading the Migration Toolkit for Containers
include::modules/common-attributes.adoc[]
:context: migrating-4-1-4
:migrating-4-1-4:
toc::[]
You can install the {mtc-full} on an {product-title} {product-version} target cluster and on a 4.1 source cluster.
{mtc-short} is installed on the target cluster by default. You can install the {mtc-short} link:https://access.redhat.com/articles/5064151[on an {product-title} 3 cluster or on a remote cluster].
[id="installing-mtc_{context}"]
== Installing the {mtc-full} in a connected environment
You can install the {mtc-full} ({mtc-short}) in a connected environment.
[IMPORTANT]
====
You must install the same {mtc-short} version on all clusters.
====
:!migrating-4-1-4:
:context: target-4-1-4
:target-4-1-4:
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+2]
:target-4-1-4!:
:context: source-4-1-4
:source-4-1-4:
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+2]
:source-4-1-4!:
:context: disconnected-4-1-4
:disconnected-4-1-4:
[id="installing-mtc_{context}"]
== Installing the {mtc-full} in a restricted environment
You can install the {mtc-full} ({mtc-short}) in a restricted environment.
[IMPORTANT]
====
You must install the same {mtc-short} version on all clusters.
====
[id="creating-local-operator-catalog_{context}"]
=== Creating a local Operator catalog
You can create a mirror image of the Operator catalog, push the image to a local registry, and then install the {mtc-full} Operator by using the {product-title} web console.
include::modules/olm-restricted-networks-configuring-operatorhub.adoc[leveloffset=+3]
include::modules/olm-pruning-index-image.adoc[leveloffset=+3]
include::modules/olm-mirroring-catalog.adoc[leveloffset=+3]
include::modules/olm-creating-catalog-from-index.adoc[leveloffset=+3]
:!disconnected-4-1-4:
:context: disconnected-target-4-1-4
:disconnected-target-4-1-4:
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+2]
:disconnected-target-4-1-4!:
:context: disconnected-source-4-1-4
:disconnected-source-4-1-4:
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+2]
:disconnected-source-4-1-4!:
:context: migrating-4-1-4
:migrating-4-1-4:
[id="upgrading-the-mtc_{context}"]
== Upgrading the {mtc-full}
You can upgrade the {mtc-full} ({mtc-short}) by using the {product-title} web console.
[IMPORTANT]
====
You must ensure that the same {mtc-short} version is installed on all clusters.
If you are upgrading {mtc-short} version 1.3, you must perform an additional procedure to update the `MigPlan` custom resource (CR).
====
include::modules/migration-upgrading-mtc-on-ocp-4.adoc[leveloffset=+2]
include::modules/migration-upgrading-from-mtc-1-3.adoc[leveloffset=+2]
:!migrating-4-1-4:

1
migration/migrating_4_1_4/images
View File

@@ -1 +0,0 @@
../../images

28
migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc
View File

@@ -1,28 +0,0 @@
[id="migrating-application-workloads-4-1-4"]
= About the {mtc-full}
include::modules/common-attributes.adoc[]
:context: migrating-4-1-4
:migrating-4-1-4:
toc::[]
You can migrate application workloads from {product-title} 4.1 to {product-version} with the {mtc-full} ({mtc-short}). {mtc-short} enables you to control the migration and to minimize application downtime.
[NOTE]
====
You can migrate between {product-title} clusters of the same version, for example, from 4.1 to 4.1, as long as the source and target clusters are configured correctly.
{mtc-short} is installed on the target cluster by default. You can configure the {mtc-full} Operator to install the {mtc-short} link:https://access.redhat.com/articles/5064151[on a remote cluster].
====
The {mtc-short} web console and API, based on Kubernetes custom resources, enable you to migrate stateful and stateless application workloads at the granularity of a namespace.
{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.
You can use migration hooks to run Ansible playbooks at certain points during the migration. The hooks are added when you create a migration plan.
include::modules/migration-mtc-workflow.adoc[leveloffset=+1]
include::modules/migration-mtc-custom-resources.adoc[leveloffset=+1]
include::modules/migration-understanding-data-copy-methods.adoc[leveloffset=+1]
include::modules/migration-about-migration-hooks.adoc[leveloffset=+1]
:!migrating-4-1-4:

78
migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
View File

@@ -1,78 +0,0 @@
[id="migrating-applications-with-cam-4-1-4"]
= Migrating your applications
include::modules/common-attributes.adoc[]
:context: migrating-4-1-4
:migrating-4-1-4:
toc::[]
You can migrate your applications by using the {mtc-full} ({mtc-short}) web console or on the command line.
include::modules/migration-prerequisites.adoc[leveloffset=+1]
include::modules/migration-creating-ca-bundle.adoc[leveloffset=+2]
include::modules/migration-configuring-proxy-for-dvm.adoc[leveloffset=+2]
include::modules/migration-writing-ansible-playbook-hook.adoc[leveloffset=+2]
[id="migrating-applications-additional-resources_{context}"]
=== Additional resources
* xref:../../migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc#migration-about-migration-hooks_migrating-4-1-4[About migration hooks]
* xref:../../migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc#mighook_migrating-4-1-4[MigHook custom resource]
* xref:../../migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc#migplan_migrating-4-1-4[MigPlan custom resource]
[id="migrating-applications-mtc-web-console_{context}"]
== Migrating your applications using the {mtc-short} web console
You can configure clusters and a replication repository by using the {mtc-short} web console. Then, you can create and run a migration plan.
include::modules/migration-launching-cam.adoc[leveloffset=+2]
include::modules/migration-adding-cluster-to-cam.adoc[leveloffset=+2]
include::modules/migration-adding-replication-repository-to-cam.adoc[leveloffset=+2]
include::modules/migration-creating-migration-plan-cam.adoc[leveloffset=+2]
include::modules/migration-running-migration-plan-cam.adoc[leveloffset=+2]
[id="migrating-applications-mtc-cli_{context}"]
== Migrating your applications from the command line
You can migrate your applications on the command line by using the {mtc-short} custom resources (CRs).
You can migrate applications from a local cluster to a remote cluster, from a remote cluster to a local cluster, and between remote clusters.
[discrete]
=== {mtc-short} terminology
The following terms are relevant for configuring clusters:
* `host` cluster:
** The `migration-controller` pod runs on the `host` cluster.
** A `host` cluster does not require an exposed secure registry route for direct image migration.
* Local cluster: The local cluster is often the same as the `host` cluster but this is not a requirement.
* Remote cluster:
** A remote cluster must have an exposed secure registry route for direct image migration.
** A remote cluster must have a `Secret` CR containing the `migration-controller` service account token.
The following terms are relevant for performing a migration:
* Source cluster: Cluster from which the applications are migrated.
* Destination cluster: Cluster to which the applications are migrated.
include::modules/migration-migrating-applications-api.adoc[leveloffset=+2]
include::modules/migration-mtc-cr-manifests.adoc[leveloffset=+2]
[id="migrating-applications-mtc-cli-additional-resources_{context}"]
== Additional resources
* xref:../../registry/securing-exposing-registry.adoc#registry-exposing-secure-registry-manually_securing-exposing-registry[Exposing a secure registry manually on an {product-title} 4 cluster]
* xref:../../migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc#file-system-copy-method_migrating-4-1-4[{mtc-short} file system copy method]
* xref:../../migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc#snapshot-copy-method_migrating-4-1-4[{mtc-short} snapshot copy method]
* xref:../../migration/migrating_4_1_4/troubleshooting-4-1-4.adoc#migration-viewing-migration-crs_migrating-4-1-4[Viewing migration custom resources]
[id="configuring-migration-plan_{context}"]
== Configuring a migration plan
You can increase the number of objects to be migrated or exclude resources from the migration.
include::modules/migration-changing-migration-plan-limits.adoc[leveloffset=+2]
include::modules/migration-excluding-resources.adoc[leveloffset=+2]
:!migrating-4-1-4:

1
migration/migrating_4_1_4/modules
View File

@@ -1 +0,0 @@
../../modules

44
migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
View File

@@ -1,44 +0,0 @@
[id="troubleshooting-4-1-4"]
= Troubleshooting
include::modules/common-attributes.adoc[]
:context: migrating-4-1-4
:migrating-4-1-4:
toc::[]
You can view the {mtc-full} ({mtc-short}) custom resources and download logs to troubleshoot a failed migration.
If the application was stopped during the failed migration, you must roll back the migration to prevent data corruption.
[NOTE]
====
Manual rollback is not required if the application was not stopped during migration because the original application is still running on the source cluster.
====
include::modules/migration-viewing-migration-crs.adoc[leveloffset=+1]
include::modules/migration-using-mig-log-reader.adoc[leveloffset=+1]
include::modules/migration-downloading-logs.adoc[leveloffset=+1]
include::modules/migration-updating-deprecated-gvks.adoc[leveloffset=+1]
include::modules/migration-error-messages.adoc[leveloffset=+1]
include::modules/migration-dvm-error-node-selectors.adoc[leveloffset=+1]
include::modules/migration-debugging-velero-resources.adoc[leveloffset=+1]
include::modules/migration-partial-failure-velero.adoc[leveloffset=+2]
include::modules/migration-using-must-gather.adoc[leveloffset=+1]
[id="rolling-back-migration_{context}"]
== Rolling back a migration
You can roll back a migration by using the {mtc-short} web console or the CLI.
include::modules/migration-rolling-back-migration-web-console.adoc[leveloffset=+2]
include::modules/migration-rolling-back-migration-cli.adoc[leveloffset=+2]
include::modules/migration-known-issues.adoc[leveloffset=+1]
[id="troubleshooting-additional-resources_{context}"]
== Additional resources
* xref:../../migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc#migration-mtc-workflow_migrating-4-1-4[{mtc-short} workflow]
* xref:../../migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc#migration-mtc-custom-resources_migrating-4-1-4[{mtc-short} custom resources]
:!migrating-4-1-4:

33
migration/migrating_4_2_4/configuring-replication-repository-4-2-4.adoc
View File

@@ -1,33 +0,0 @@
[id="configuring-replication-repository-4-2-4"]
= Configuring object storage for a replication repository
include::modules/common-attributes.adoc[]
:context: migrating-4-2-4
:migrating-4-2-4:
toc::[]
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:../../migration/migrating_4_2_4/migrating-application-workloads-4-2-4.adoc#migration-understanding-data-copy-methods_migrating-4-2-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:../../migration/migrating_4_2_4/configuring-replication-repository-4-2-4.adoc#migration-configuring-mcg_migrating-4-2-4[Multi-Cloud Object Gateway (MCG)]
* xref:../../migration/migrating_4_2_4/configuring-replication-repository-4-2-4.adoc#migration-configuring-aws-s3_migrating-4-2-4[Amazon Web Services (AWS) S3]
* xref:../../migration/migrating_4_2_4/configuring-replication-repository-4-2-4.adoc#migration-configuring-gcp_migrating-4-2-4[Google Cloud Provider (GCP)]
* xref:../../migration/migrating_4_2_4/configuring-replication-repository-4-2-4.adoc#migration-configuring-azure_migrating-4-2-4[Microsoft Azure]
* Generic S3 object storage, for example, Minio or Ceph S3
In a restricted environment, you can create an internally hosted replication repository.
.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=+1]
include::modules/migration-configuring-aws-s3.adoc[leveloffset=+1]
include::modules/migration-configuring-gcp.adoc[leveloffset=+1]
include::modules/migration-configuring-azure.adoc[leveloffset=+1]
:!migrating-4-2-4:

84
migration/migrating_4_2_4/deploying-cam-4-2-4.adoc
View File

@@ -1,84 +0,0 @@
[id="deploying-cam-4-2-4"]
= Installing and upgrading the Migration Toolkit for Containers
include::modules/common-attributes.adoc[]
:context: migrating-4-2-4
:migrating-4-2-4:
toc::[]
You can install the {mtc-full} Operator on your {product-title} {product-version} target cluster and 4.2 source cluster.
{mtc-short} is installed on the target cluster by default. You can install {mtc-short} link:https://access.redhat.com/articles/5064151[on an {product-title} 3 cluster or on a remote cluster].
[IMPORTANT]
====
You must install the same {mtc-short} version on all clusters.
====
[id="installing-mtc_{context}"]
== Installing the {mtc-full} in a connected environment
You can install the {mtc-full} ({mtc-short}) in a connected environment.
:!migrating-4-2-4:
:context: target-4-2-4
:target-4-2-4:
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+2]
:target-4-2-4!:
:context: source-4-2-4
:source-4-2-4:
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+2]
:source-4-2-4!:
:context: disconnected-4-2-4
:disconnected-4-2-4:
[id="installing-mtc_{context}"]
== Installing the {mtc-full} in a restricted environment
You can install the {mtc-full} ({mtc-short}) in a restricted environment.
[IMPORTANT]
====
You must install the same {mtc-short} version on all clusters.
====
[id="creating-local-operator-catalog_{context}"]
=== Creating a local Operator catalog
You can create a mirror image of the Operator catalog, push the image to a local registry, and then install the {mtc-full} Operator by using the {product-title} web console.
include::modules/olm-restricted-networks-configuring-operatorhub.adoc[leveloffset=+3]
include::modules/olm-pruning-index-image.adoc[leveloffset=+3]
include::modules/olm-mirroring-catalog.adoc[leveloffset=+3]
include::modules/olm-creating-catalog-from-index.adoc[leveloffset=+3]
:!disconnected-4-2-4:
:context: disconnected-target-4-2-4
:disconnected-target-4-2-4:
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+2]
:disconnected-target-4-2-4!:
:context: disconnected-source-4-2-4
:disconnected-source-4-2-4:
include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+2]
:disconnected-source-4-2-4!:
:context: migrating-4-2-4
:migrating-4-2-4:
[id="upgrading-the-mtc_{context}"]
== Upgrading the {mtc-full}
You can upgrade the {mtc-full} ({mtc-short}) by using the {product-title} web console.
[IMPORTANT]
====
You must ensure that the same {mtc-short} version is installed on all clusters.
If you are upgrading {mtc-short} version 1.3, you must perform an additional procedure to update the `MigPlan` custom resource (CR).
====
include::modules/migration-upgrading-mtc-on-ocp-4.adoc[leveloffset=+2]
include::modules/migration-upgrading-from-mtc-1-3.adoc[leveloffset=+2]
:!migrating-4-2-4:

1
migration/migrating_4_2_4/images
View File

@@ -1 +0,0 @@
../../images

28
migration/migrating_4_2_4/migrating-application-workloads-4-2-4.adoc
View File

@@ -1,28 +0,0 @@
[id="migrating-application-workloads-4-2-4"]
= About the {mtc-full}
include::modules/common-attributes.adoc[]
:context: migrating-4-2-4
:migrating-4-2-4:
toc::[]
You can migrate application workloads from {product-title} 4.2 to {product-version} with the {mtc-full} ({mtc-short}). {mtc-short} enables you to control the migration and to minimize application downtime.
[NOTE]
====
You can migrate between {product-title} clusters of the same version, for example, from 4.2 to 4.2 or from 4.3 to 4.3, as long as the source and target clusters are configured correctly.
{mtc-short} is installed on the target cluster by default. You can configure the {mtc-full} Operator to install the {mtc-short} link:https://access.redhat.com/articles/5064151[on a remote cluster].
====
The {mtc-short} web console and API, based on Kubernetes custom resources, enable you to migrate stateful and stateless application workloads at the granularity of a namespace.
{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.
You can use migration hooks to run Ansible playbooks at certain points during the migration. The hooks are added when you create a migration plan.
include::modules/migration-mtc-workflow.adoc[leveloffset=+1]
include::modules/migration-mtc-custom-resources.adoc[leveloffset=+1]
include::modules/migration-understanding-data-copy-methods.adoc[leveloffset=+1]
include::modules/migration-about-migration-hooks.adoc[leveloffset=+1]
:!migrating-4-2-4:

1
migration/migrating_4_2_4/modules
View File

@@ -1 +0,0 @@
../../modules

2
modules/deploy-red-hat-openshift-container-storage.adoc
View File

@@ -45,6 +45,6 @@
|link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.5/html/troubleshooting_openshift_container_storage/index[Troubleshooting OpenShift Container Storage 4.5]
|Migrating your {product-title} cluster from version 3 to version 4
|link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.5/html/migration/index[Migration]
|link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/migrating_from_ocp_3_to_4/index[Migration]
|===

3
modules/migration-about-migration-hooks.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-application-workloads-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc.adoc
[id="migration-about-migration-hooks_{context}"]
= About migration hooks

3
modules/migration-adding-cluster-to-cam.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-adding-cluster-to-cam_{context}"]
= Adding a cluster to the {mtc-short} web console

3
modules/migration-adding-replication-repository-to-cam.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-adding-replication-repository-to-cam_{context}"]
= Adding a replication repository to the {mtc-short} web console

3
modules/migration-changing-migration-plan-limits.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-changing-migration-plan-limits_{context}"]
= Increasing limits for large migrations

4
modules/migration-configuring-aws-s3.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/installing-3-4.adoc
// * migration/migrating_4_1_4/configuring-replication-repository-4-1-4.adoc
// * migration/migrating_4_2_4/configuring-replication-repository-4-2-4.adoc
// * migration-toolkit-for-containers/installing-mtc.adoc
// * migration-toolkit-for-containers/installing-mtc-restricted.adoc
[id="migration-configuring-aws-s3_{context}"]
= Configuring Amazon Web Services S3

4
modules/migration-configuring-azure.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/installing-3-4.adoc
// * migration/migrating_4_1_4/configuring-replication-repository-4-1-4.adoc
// * migration/migrating_4_2_4/configuring-replication-repository-4-2-4.adoc
// * migration-toolkit-for-containers/installing-mtc.adoc
// * migration-toolkit-for-containers/installing-mtc-restricted.adoc
[id="migration-configuring-azure_{context}"]
= Configuring Microsoft Azure Blob

4
modules/migration-configuring-gcp.adoc
View File

@@ -1,8 +1,8 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/installing-3-4.adoc
// * migration/migrating_4_1_4/configuring-replication-repository-4-1-4.adoc
// * migration/migrating_4_2_4/configuring-replication-repository-4-2-4.adoc
// * migration-toolkit-for-containers/installing-mtc.adoc
// * migration-toolkit-for-containers/installing-mtc-restricted.adoc
[id="migration-configuring-gcp_{context}"]
= Configuring Google Cloud Provider

4
modules/migration-configuring-mcg.adoc
View File

@@ -2,8 +2,8 @@
//
// * migrating_from_ocp_3_to_4/installing-3-4.adoc
// * migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc
// * migration/migrating_4_1_4/configuring-replication-repository-4-1-4.adoc
// * migration/migrating_4_2_4/configuring-replication-repository-4-2-4.adoc
// * migration-toolkit-for-containers/installing-mtc.adoc
// * migration-toolkit-for-containers/installing-mtc-restricted.adoc
[id="migration-configuring-mcg_{context}"]
= Configuring Multi-Cloud Object Gateway

3
modules/migration-configuring-proxy-for-dvm.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-configuring-proxy-for-dvm_{context}"]
= Configuring a proxy for direct volume migration

3
modules/migration-creating-ca-bundle.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="creating-ca-bundle_{context}"]
= Creating a CA certificate bundle file

3
modules/migration-creating-migration-plan-cam.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-creating-migration-plan-cam_{context}"]
= Creating a migration plan in the {mtc-short} web console

3
modules/migration-debugging-velero-resources.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-debugging-velero-resources_{context}"]
= Using the Velero CLI to debug Backup and Restore CRs

3
modules/migration-downloading-logs.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-downloading-logs_{context}"]
= Downloading migration logs

3
modules/migration-dvm-error-node-selectors.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-dvm-error-node-selectors_{context}"]
= Direct volume migration does not complete

3
modules/migration-error-messages.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-error-messages_{context}"]
= Error messages and resolutions

3
modules/migration-excluding-resources.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-excluding-resources_{context}"]
= Excluding resources from a migration plan

4
modules/migration-installing-mtc-on-ocp-3.adoc
View File

@@ -2,8 +2,8 @@
//
// * migrating_from_ocp_3_to_4/installing-3-4.adoc
// * migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc
// * migration/migrating_4_1_4/deploying-cam-4-1-4.adoc
// * migration/migrating_4_2_4/deploying-cam-4-2-4.adoc
// * migration-toolkit-for-containers/installing-mtc.adoc
// * migration-toolkit-for-containers/installing-mtc-restricted.adoc
[id="migration-installing-mtc-on-ocp-3_{context}"]
= Installing the {mtc-full} Operator on {product-title} 3

29
modules/migration-installing-mtc-on-ocp-4.adoc
View File

@@ -2,17 +2,19 @@
//
// * migrating_from_ocp_3_to_4/installing-3-4.adoc
// * migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc
// * migration-toolkit-for-containers/installing-mtc.adoc
// * migration-toolkit-for-containers/installing-mtc-restricted.adoc
[id="migration-installing-mtc-on-ocp-4_{context}"]
= Installing the {mtc-full} Operator on {product-title} {product-version}
= Installing the {mtc-full} Operator on {product-title} 4
You can install the {mtc-short} Operator on {product-title} {product-version} by using the {product-title} web console.
You can install the {mtc-short} Operator on {product-title} 4 by using the {product-title} web console.
.Prerequisites
* You must be logged in as a user with `cluster-admin` privileges on all clusters.
ifdef::installing-restricted-3-4[]
* You must have access to an Operator catalog in a local registry.
ifdef::installing-restricted-3-4,installing-mtc-restricted[]
* You must create an Operator catalog from a mirror image in a local registry. See xref:../operators/admin/olm-restricted-networks.adoc[Using Operator Lifecycle Manager on restricted networks] for instructions.
endif::[]
.Procedure
@@ -20,11 +22,13 @@ endif::[]
. In the {product-title} web console, click *Operators* -> *OperatorHub*.
. Use the *Filter by keyword* field to find the *{mtc-full} Operator*.
. Select the *{mtc-full} Operator* and click *Install*.
ifdef::installing-3-4,installing-mtc[]
+
[NOTE]
====
Do not change the subscription approval option to *Automatic*. The {mtc-full} version must be the same on the source and the target clusters.
====
endif::[]
. Click *Install*.
+
@@ -33,8 +37,7 @@ On the *Installed Operators* page, the *{mtc-full} Operator* appears in the *ope
. Click *{mtc-full} Operator*.
. Under *Provided APIs*, locate the *Migration Controller* tile, and click *Create Instance*.
ifdef::source-4-1-4[]
. Update the following parameters in the `migration-controller` custom resource manifest:
. If you do not want to run the {mtc-short} web console and the `Migration Controller` pod on the cluster, update the following parameters in the `migration-controller` custom resource manifest:
+
[source,yaml]
----
@@ -45,19 +48,7 @@ spec:
...
deprecated_cors_configuration: true <1>
----
<1> Add the `deprecated_cors_configuration` parameter and its value.
endif::[]
ifdef::source-4-2-4[]
. Update the following parameters in in the `migration-controller` custom resource manifest:
+
[source,yaml]
----
spec:
...
migration_controller: false
migration_ui: false
----
endif::[]
<1> This parameter is required only for {product-title} 4.1.
. Click *Create*.
. Click *Workloads* -> *Pods* to verify that the {mtc-short} pods are running.

3
modules/migration-known-issues.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-known-issues_{context}"]
= Known issues

3
modules/migration-launching-cam.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-launching-cam_{context}"]
= Launching the {mtc-short} web console

3
modules/migration-migrating-applications-api.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-migrating-applications-api_{context}"]
= Migrating your applications with the {mtc-full} API

3
modules/migration-mtc-cr-manifests.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-mtc-cr-manifests_{context}"]
= {mtc-short} custom resource manifests

3
modules/migration-mtc-custom-resources.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-application-workloads-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc.adoc
[id="migration-mtc-custom-resources_{context}"]
= {mtc-full} custom resources

3
modules/migration-mtc-workflow.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-application-workloads-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc.adoc
[id="migration-mtc-workflow_{context}"]
= {mtc-full} workflow

3
modules/migration-partial-failure-velero.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-partial-failure-velero_{context}"]
= Debugging a partial migration failure

3
modules/migration-prerequisites.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-prerequisites_{context}"]
= Prerequisites

3
modules/migration-rolling-back-migration-cli.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-rolling-back-migration-cli_{context}"]
== Rolling back a migration from the CLI

3
modules/migration-rolling-back-migration-web-console.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-rolling-back-migration-web-console_{context}"]
= Rolling back a migration in the {mtc-short} web console

3
modules/migration-running-migration-plan-cam.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-running-migration-plan-cam_{context}"]
= Running a migration plan in the {mtc-short} web console

3
modules/migration-understanding-data-copy-methods.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-application-workloads-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-application-workloads-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc.adoc
[id="migration-understanding-data-copy-methods_{context}"]
= About data copy methods

1
modules/migration-updating-deprecated-gvks.adoc
View File

@@ -1,6 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-gvk-incompatibility_{context}"]
= Updating deprecated APIs

1
modules/migration-updating-deprecated-internal-images.adoc
View File

@@ -1,6 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-updating-deprecated-internal-images_{context}"]
= Updating deprecated internal images with podman

3
modules/migration-upgrading-from-mtc-1-3.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/upgrading-3-4.adoc
// * migration/migrating_4_1_4/deploying-cam-4-1-4.adoc
// * migration/migrating_4_1_4/deploying-cam-4-2-4.adoc
// * migration-toolkit-for-containers/upgrading-mtc.adoc
[id="migration-upgrading-from-mtc-1-3_{context}"]
= Upgrading {mtc-short} 1.3 to {mtc-version}

3
modules/migration-upgrading-mtc-on-ocp-3.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/upgrading-3-4.adoc
// * migration/migrating_4_1_4/deploying-cam-4-1-4.adoc
// * migration/migrating_4_1_4/deploying-cam-4-2-4.adoc
// * migration-toolkit-for-containers/upgrading-mtc.adoc
[id="migration-upgrading-mtc-on-ocp-3_{context}"]
= Upgrading the {mtc-full} on {product-title} 3

3
modules/migration-upgrading-mtc-on-ocp-4.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/upgrading-3-4.adoc
// * migration/migrating_4_1_4/deploying-cam-4-1-4.adoc
// * migration/migrating_4_1_4/deploying-cam-4-2-4.adoc
// * migration-toolkit-for-containers/upgrading-mtc.adoc
[id="migration-upgrading-mtc-on-ocp-4_{context}"]
= Upgrading the {mtc-full} on {product-title} 4

3
modules/migration-using-mig-log-reader.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-using-mig-log-reader_{context}"]
= Using the migration log reader

3
modules/migration-using-must-gather.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-using-must-gather_{context}"]
= Using must-gather to collect data

3
modules/migration-viewing-migration-crs.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
// * migration/migrating_4_1_4/troubleshooting-4-1-4.adoc
// * migration/migrating_4_2_4/troubleshooting-4-2-4.adoc
// * migration-toolkit-for-containers/troubleshooting-mtc
[id="migration-viewing-migration-crs_{context}"]
= Viewing {mtc-short} custom resources

3
modules/migration-writing-ansible-playbook-hook.adoc
View File

@@ -1,8 +1,7 @@
// Module included in the following assemblies:
//
// * migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc
// * migration/migrating_4_1_4/migrating-applications-with-cam-4-1-4.adoc
// * migration/migrating_4_2_4/migrating-applications-with-cam-4-2-4.adoc
// * migration-toolkit-for-containers/migrating-applications-with-mtc
[id="migration-writing-ansible-playbook-hook_{context}"]
= Writing an Ansible playbook for a migration hook

3
modules/olm-creating-catalog-from-index.adoc
View File

@@ -2,9 +2,6 @@
//
// * operators/admin/olm-restricted-networks.adoc
// * operators/admin/managing-custom-catalogs.adoc
// * migrating_from_ocp_3_to_4/installing-and-upgrading-3-4.adoc
// * migration/migrating_4_1_4/deploying-cam-4-1-4.adoc
// * migration/migrating_4_2_4/deploying-cam-4-2-4.adoc
ifdef::openshift-origin[]
:index-image: catalog

3
modules/olm-mirroring-catalog.adoc
View File

@@ -1,9 +1,6 @@
// Module included in the following assemblies:
//
// * operators/admin/olm-restricted-networks.adoc
// * migrating_from_ocp_3_to_4/installing-and-upgrading-3-4.adoc
// * migration/migrating_4_1_4/deploying-cam-4-1-4.adoc
// * migration/migrating_4_2_4/deploying-cam-4-2-4.adoc
ifdef::openshift-origin[]
:index-image-pullspec: quay.io/operatorhubio/catalog:latest

3
modules/olm-pruning-index-image.adoc
View File

@@ -2,9 +2,6 @@
//
// * operators/admin/olm-restricted-networks.adoc
// * operators/admin/olm-managing-custom-catalogs.adoc
// * migrating_from_ocp_3_to_4/installing-and-upgrading-3-4.adoc
// * migration/migrating_4_1_4/deploying-cam-4-1-4.adoc
// * migration/migrating_4_2_4/deploying-cam-4-2-4.adoc
ifdef::openshift-origin[]
:catalog-name: catalog