From 87d15c7fa8fbfba283ee229c8ae80837e72f8bbe Mon Sep 17 00:00:00 2001 From: Avital Pinnick Date: Sun, 5 Dec 2021 13:44:01 +0200 Subject: [PATCH] BZ2028880: Clarify that MTC installation is for OCP4 --- migration_toolkit_for_containers/about-mtc.adoc | 5 +++++ .../installing-mtc-restricted.adoc | 5 +++++ migration_toolkit_for_containers/installing-mtc.adoc | 5 ++++- modules/migration-compatibility-guidelines.adoc | 2 +- 4 files changed, 15 insertions(+), 2 deletions(-) diff --git a/migration_toolkit_for_containers/about-mtc.adoc b/migration_toolkit_for_containers/about-mtc.adoc index 5ef8a113dd..727cbe590f 100644 --- a/migration_toolkit_for_containers/about-mtc.adoc +++ b/migration_toolkit_for_containers/about-mtc.adoc @@ -7,6 +7,11 @@ toc::[] The {mtc-full} ({mtc-short}) enables you to migrate stateful application workloads between {product-title} 4 clusters at the granularity of a namespace. +[NOTE] +==== +If you are migrating from {product-title} 3, see xref:../migrating_from_ocp_3_to_4/about-migrating-from-3-to-4.adoc#about-migrating-from-3-to-4[About migrating from {product-title} 3 to 4] and xref:../migrating_from_ocp_3_to_4/installing-3-4.adoc#migration-installing-legacy-operator_installing-3-4[Installing the legacy {mtc-full} Operator on {product-title} 3]. +==== + You can migrate applications within the same cluster by using state migration. {mtc-short} provides a web console and an API, based on Kubernetes custom resources, to help you control the migration and minimize application downtime. diff --git a/migration_toolkit_for_containers/installing-mtc-restricted.adoc b/migration_toolkit_for_containers/installing-mtc-restricted.adoc index 887c413624..0c7038dbe6 100644 --- a/migration_toolkit_for_containers/installing-mtc-restricted.adoc +++ b/migration_toolkit_for_containers/installing-mtc-restricted.adoc @@ -19,6 +19,11 @@ By default, the {mtc-short} web console and the `Migration Controller` pod run o * {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. ++ +[NOTE] +==== +To install {mtc-short} on {product-title} 3, see xref:../migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc#migration-installing-legacy-operator_installing-restricted-3-4[Installing the legacy {mtc-full} Operator on {product-title} 3]. +==== . Configure object storage to use as a replication repository. diff --git a/migration_toolkit_for_containers/installing-mtc.adoc b/migration_toolkit_for_containers/installing-mtc.adoc index 5c11a3a503..0dcda3a24f 100644 --- a/migration_toolkit_for_containers/installing-mtc.adoc +++ b/migration_toolkit_for_containers/installing-mtc.adoc @@ -8,7 +8,10 @@ toc::[] You can install the {mtc-full} ({mtc-short}) on {product-title} 4. -After you manually install the legacy {mtc-full} Operator on the {product-title} 4 source cluster, you install the {mtc-full} Operator on the {product-title} {product-version} target cluster by using the Operator Lifecycle Manager. +[NOTE] +==== +To install {mtc-short} on {product-title} 3, see xref:../migrating_from_ocp_3_to_4/installing-3-4.adoc#migration-installing-legacy-operator_installing-3-4[Installing 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[remote cluster]. diff --git a/modules/migration-compatibility-guidelines.adoc b/modules/migration-compatibility-guidelines.adoc index 05544af610..ea8f6eef97 100644 --- a/modules/migration-compatibility-guidelines.adoc +++ b/modules/migration-compatibility-guidelines.adoc @@ -8,7 +8,7 @@ [id="migration-compatibility-guidelines_{context}"] = Compatibility guidelines -You must install the {mtc-full} ({mtc-short}) version that is compatible with your {product-title} version. +You must install the {mtc-full} ({mtc-short}) Operator that is compatible with your {product-title} version. You cannot install {mtc-short} {mtc-version} on {product-title} 4.5, or earlier versions, because the custom resource definition API versions are incompatible.