Merge pull request #30172 from apinnick/bz1933188-mtc-dvm-proxy

BZ1933188: DVM does not work with source cluster proxy (MTC 1.4.0)

Author: apinnick

modules/migration-adding-cluster-to-cam.adoc

@@ -11,10 +11,10 @@ You can add a cluster to the {mtc-full} ({mtc-short}) web console.
 
 .Prerequisites
 
-If you are using Azure snapshots to copy data:
-
-* You must provide the Azure resource group name when you add the source cluster.
-* The source and target clusters must be in the same Azure resource group and in the same location.
+* Optional: If you are using direct image migration, the source cluster must not have an HTTP proxy configured.
+* Optional: If you are using Azure snapshots to copy data:
+** You must specify the Azure resource group name for the source cluster.
+** The source and target clusters must be in the same Azure resource group and in the same location.
 
 .Procedure
 

modules/migration-creating-migration-plan-cam.adoc

@@ -14,11 +14,13 @@ You can use _direct image migration_ and _direct volume migration_ to migrate im
 .Prerequisites
 
 * You must add source and target clusters and a replication repository to the {mtc-short} web console.
-* The clusters must have network access to each other.
-* The clusters must have network access to the replication repository.
-* The clusters must be able to communicate using OpenShift routes on port 443.
-* The clusters must have no `Critical` conditions.
-* The clusters must be in a `Ready` state.
+* Clusters:
+** The clusters must have network access to each other.
+** The clusters must have network access to the replication repository.
+** The clusters must be able to communicate using OpenShift routes on port 443.
+** The clusters must have no `Critical` conditions.
+** The clusters must be in a `Ready` state.
+
 * The migration plan name must not exceed 253 lower-case alphanumeric characters (`a-z, 0-9`) and must not contain spaces or underscores (`_`).
 * PV `Move` copy method: The clusters must have network access to the remote volume.
 * PV `Snapshot` copy method:
@@ -28,12 +30,13 @@ You can use _direct image migration_ and _direct volume migration_ to migrate im
 
 * Direct image migration:
 ** The source cluster must have its internal registry exposed to external traffic.
-** The exposed registry route of the source cluster must be added to the cluster configuration using the {mtc-short} web console or with the `exposedRegistryPath` parameter in the `MigCluster` CR manifest.
+** The exposed registry route of the source cluster must be added to the cluster configuration by using either the {mtc-short} web console or the `exposedRegistryPath` parameter in the `MigCluster` CR manifest.
 
 * Direct volume migration:
 ** The PVs to be migrated must be valid.
 ** The PVs must be in a `bound` state.
-** The PV migration method must be `Copy` and the copy method must be `filesystem`.
+** The PVs must be copied by using the file system copy method.
+** The source cluster must not have an HTTP proxy configured.
 
 .Procedure
 

modules/migration-migrating-applications-api.adoc

@@ -44,6 +44,7 @@ You can create multiple `MigMigration` CRs for a single `MigPlan` CR for the fol
 * The _version_ of the installed {mtc-full} Operator must be the same on all clusters.
 * You must configure an object storage as a replication repository.
 * If you are using direct image migration, you must expose a secure registry route on all remote clusters.
+* If you are using direct volume migration, the source cluster must not have an HTTP proxy configured.
 
 .Procedure