From c9540a3de30ecd60d930ea5eb0d99faa3744fa66 Mon Sep 17 00:00:00 2001 From: Avital Pinnick Date: Mon, 7 Jun 2021 16:40:16 +0300 Subject: [PATCH] Update modules/migration-creating-migration-plan-cam.adoc Co-authored-by: Bob Furu --- modules/migration-creating-migration-plan-cam.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/migration-creating-migration-plan-cam.adoc b/modules/migration-creating-migration-plan-cam.adoc index 187cd54794..62d114c203 100644 --- a/modules/migration-creating-migration-plan-cam.adoc +++ b/modules/migration-creating-migration-plan-cam.adoc @@ -15,7 +15,7 @@ You can create a migration plan in the {mtc-full} ({mtc-short}) web console. * You must ensure that the same {mtc-short} version is installed on all clusters. * You must add the clusters and the replication repository to the {mtc-short} web console. * If you want to use the _move_ data copy method to migrate a persistent volume (PV), the source and target clusters must have uninterrupted network access to the remote volume. -* If you want to use direct image migration, you must specify the exposed route to the image registry of the source cluster by using the {mtc-short} web console or by updating the `MigCluster` custom resource manifest. +* If you want to use direct image migration, you must specify the exposed route to the image registry of the source cluster. This can be done by using the {mtc-short} web console or by updating the `MigCluster` custom resource manifest. .Procedure