Merge pull request #35761 from apinnick/mig-802-legacy-operator

MIG-802: legacy MTC operator for OCP 3.7 to 4.5 (MTC 1.5.1)

Author: apinnick

migrating_from_ocp_3_to_4/about-mtc-3-4.adoc

@@ -5,7 +5,7 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-The {mtc-full} ({mtc-short}) enables you to migrate stateful application workloads from {product-title} 3.7, 3.9, 3.10, or 3.11 to {product-version} at the granularity of a namespace.
+The {mtc-full} ({mtc-short}) enables you to migrate stateful application workloads from {product-title} 3 to {product-version} at the granularity of a namespace.
 
 [IMPORTANT]
 ====

migrating_from_ocp_3_to_4/installing-3-4.adoc

@@ -6,20 +6,17 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-You can install the {mtc-full} ({mtc-short}) on {product-title} 3 and on {product-title} {product-version} clusters.
+You can install the {mtc-full} ({mtc-short}) on {product-title} 3 and 4.
 
-[IMPORTANT]
-====
-You must install the same {mtc-short} version on all clusters.
-====
+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.
 
 include::modules/migration-compatibility-guidelines.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-installing-mtc-on-ocp-3.adoc[leveloffset=+1]
 include::modules/migration-configuring-proxies.adoc[leveloffset=+1]
 
 For more information, see xref:../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
@@ -31,10 +28,6 @@ You must configure an object storage to use as a replication repository. The {mt
 
 {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.
 
-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:
 
 * xref:../migrating_from_ocp_3_to_4/installing-3-4.adoc#migration-configuring-mcg_installing-3-4[Multicloud Object Gateway]
@@ -43,17 +36,21 @@ The following storage providers are supported:
 * 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="{context}_configuring-replication-repository-additional-resources"]
-[discrete]
-=== Additional resources for configuring a replication repository
+[id="replication-repository-prerequisites_{context}"]
+=== Prerequisites
 
-* 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]
+* 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]
 
+[id="{context}_configuring-replication-repository-additional-resources"]
+=== Additional resources for configuring a replication repository
+
+* 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]
 :installing-3-4!:

migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc

@@ -6,22 +6,17 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-You can install the {mtc-full} ({mtc-short}) on {product-title} 3 and on {product-title} {product-version} in a restricted network environment.
+You can install the {mtc-full} ({mtc-short}) on {product-title} 3 and 4 in a restricted network environment.
 
-[IMPORTANT]
-====
-You must install the same {mtc-short} version on all clusters.
-====
+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].
+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.
 
 include::modules/migration-compatibility-guidelines.adoc[leveloffset=+1]
 include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
-include::modules/migration-installing-mtc-on-ocp-3.adoc[leveloffset=+1]
+include::modules/migration-installing-legacy-operator.adoc[leveloffset=+1]
 include::modules/migration-configuring-proxies.adoc[leveloffset=+1]
 
 For more information, see xref:../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
@@ -33,18 +28,19 @@ The Multicloud Object Gateway is the only supported option for a restricted netw
 
 {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.
 
-All clusters must have uninterrupted network access to the replication repository.
+[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.
 
-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]
 
 [id="{context}_configuring-replication-repository-additional-resources"]
-[discrete]
 === Additional resources for configuring a replication repository
 
 * link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.8/html-single/planning_your_deployment/index#disconnected-environment_rhocs[Disconnected environment] in the Red Hat OpenShift Container Storage 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-configuring-mcg.adoc[leveloffset=+2]
 :installing-restricted-3-4!:

migrating_from_ocp_3_to_4/premigration-checklists-3-4.adoc

@@ -11,8 +11,9 @@ Before you migrate your application workloads with the {mtc-full} ({mtc-short}),
 == Source cluster checklist
 
 * [ ] The cluster meets the link:https://docs.openshift.com/container-platform/3.11/install/prerequisites.html#hardware[minimum hardware requirements].
-* [ ] The {product-title} version is 3.7, 3.9, 3.10, or 3.11.
-* [ ] The {mtc-short} version is the same on all clusters.
+* [ ] You have installed the correct legacy {mtc-full} Operator version:
+** `operator-3.7.yml` on {product-title} version 3.7.
+** `operator.yml` on {product-title} versions 3.9 to 4.5.
 * [ ] All nodes have an active {product-title} subscription.
 * [ ] All the link:https://docs.openshift.com/container-platform/3.11/day_two_guide/run_once_tasks.html#day-two-guide-default-storage-class[run-once tasks] have been performed.
 * [ ] All the link:https://docs.openshift.com/container-platform/3.11/day_two_guide/environment_health_checks.html[environment health checks] have been performed.
@@ -66,7 +67,7 @@ $ oc get csr -A | grep pending -i
 [id="target-cluster-checklist_{context}"]
 == Target cluster checklist
 
-* [ ] The {mtc-short} version is the same on all clusters.
+* [ ] You have installed {mtc-full} Operator version 1.5.1.
 * [ ] All xref:../migrating_from_ocp_3_to_4/migrating-applications-3-4.adoc#migration-prerequisites_migrating-applications-3-4[{mtc-short} prerequisites] are met.
 * [ ] The cluster meets the minimum hardware requirements for the specific platform and installation method, for example, on xref:../installing/installing_bare_metal/installing-bare-metal.adoc#minimum-resource-requirements_installing-bare-metal[bare metal].
 * [ ] The cluster has xref:../storage/dynamic-provisioning.adoc#defining-storage-classes_dynamic-provisioning[storage classes] defined for the storage types used by the source cluster, for example, block volume, file system, or object storage.

migrating_from_ocp_3_to_4/upgrading-3-4.adoc

@@ -2,18 +2,20 @@
 = Upgrading the Migration Toolkit for Containers
 include::modules/common-attributes.adoc[]
 :context: upgrading-3-4
+:upgrading-3-4:
 
 toc::[]
 
-You can upgrade the {mtc-full} ({mtc-short}) by using the {product-title} web console.
+You can upgrade the {mtc-full} ({mtc-short}) on {product-title} {product-version} by using the Operator Lifecycle Manager.
+
+You can upgrade {mtc-short} on {product-title} versions 3.7 to 3.11 by installing the legacy {mtc-full} Operator.
 
 [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).
+If you are upgrading from {mtc-short} version 1.3 to {mtc-version}, 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-mtc-with-legacy-operator.adoc[leveloffset=+1]
 include::modules/migration-upgrading-from-mtc-1-3.adoc[leveloffset=+1]
+:upgrading-3-4!:

migration_toolkit_for_containers/about-mtc.adoc

@@ -5,7 +5,7 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-The {mtc-full} ({mtc-short}) enables you to migrate stateful application workloads between {product-title} clusters at the granularity of a namespace.
+The {mtc-full} ({mtc-short}) enables you to migrate stateful application workloads between {product-title} 4 clusters at the granularity of a namespace.
 
 {mtc-short} provides a web console and an API, based on Kubernetes custom resources, to help you control the migration and minimize application downtime.
 

migration_toolkit_for_containers/installing-mtc-restricted.adoc

@@ -8,19 +8,15 @@ 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.
-====
+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 the {product-title} 4 source cluster.
 
-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].
+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].
 
 After you have installed {mtc-short}, you must configure an object storage to use as a replication repository.
 
 include::modules/migration-compatibility-guidelines.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-configuring-proxies.adoc[leveloffset=+1]
 
 For more information, see xref:../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
@@ -32,18 +28,19 @@ The Multicloud Object Gateway is the only supported option for a restricted netw
 
 {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.
+[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.
 
-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]
 
 [id="{context}_configuring-replication-repository-additional-resources"]
-[discrete]
 === Additional resources for configuring a replication repository
 
 * link:https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.8/html-single/planning_your_deployment/index#disconnected-environment_rhocs[Disconnected environment] in the Red Hat OpenShift Container Storage documentation.
 * 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-understanding-data-copy-methods_about-mtc[About data copy methods]
 * xref:../migration_toolkit_for_containers/migrating-applications-with-mtc.adoc#migration-adding-replication-repository-to-cam_migrating-applications-with-mtc[Adding a replication repository to the {mtc-short} web console]
-
-include::modules/migration-configuring-mcg.adoc[leveloffset=+2]
 :installing-mtc-restricted!: