You can automate your migrations and modify the MigPlan and MigrationController custom resources in order to perform large-scale migrations and to improve performance.
-
For information about creating a MigCluster CR manifest for each remote cluster, see Migrating an application by using the {mtc-short} API.
-
For information about adding a cluster using the web console, see Migrating your applications by using the {mtc-short} web console
You can migrate applications with the {mtc-short} API by using the command line interface (CLI) in order to automate the migration.
modules/migration-prerequisites.adoc modules/migration-creating-registry-route-for-dim.adoc modules/migration-about-configuring-proxies.adoc modules/migration-configuring-proxies.adoc modules/migration-migrating-applications-api.adoc modules/migration-state-migration-cli.adoc
-
See Excluding PVCs from migration to select PVCs for state migration.
-
See Mapping PVCs to migrate source PV data to provisioned PVCs on the destination cluster.
-
See Migrating Kubernetes objects to migrate the Kubernetes objects that constitute an application’s state.
You can exclude, edit, and map components in the MigPlan custom resource (CR).
modules/migration-excluding-resources.adoc modules/migration-mapping-destination-namespaces-in-the-migplan-cr.adoc modules/migration-excluding-pvcs.adoc modules/migration-mapping-pvcs.adoc modules/migration-editing-pvs-in-migplan.adoc
-
For details about the
moveandcopyactions, see MTC workflow. -
For details about the
skipaction, see Excluding PVCs from migration. -
For details about the file system and snapshot copy methods, see About data copy methods.
You can edit migration plan limits, enable persistent volume resizing, or enable cached Kubernetes clients in the MigrationController custom resource (CR) for large migrations and improved performance.