1. Documentation
    2. Page history / Open an issue
×

Upgrading the Migration Toolkit for Containers

You can upgrade the Migration Toolkit for Containers (MTC) by upgrading the Migration Toolkit for Containers Operator.

If you are upgrading MTC 1.3, you must perform an additional procedure to update the MigPlan custom resource (CR).

Upgrading the Migration Toolkit for Containers on an OpenShift Container Platform 4 cluster

You can upgrade the Migration Toolkit for Containers (MTC) on an OpenShift Container Platform 4 cluster using the OpenShift Container Platform console.

If you selected the Automatic approval option when you installed the Migration Toolkit for Containers Operator, the Operator is updated automatically.

The following procedure enables you to change the Manual approval option to Automatic or to change the release channel.

Procedure

  1. In the OpenShift Container Platform console, navigate to Operators → Installed Operators.

  2. Click Migration Toolkit for Containers Operator.

  3. In the Subscription tab, change the Approval option to Automatic.

  4. Optional: Edit the Channel.

    Updating the subscription deploys the updated Migration Toolkit for Containers Operator and updates the MTC components.

  5. Under Provided APIs, locate the Migration Controller tile, and click Create Instance.

  6. If you are upgrading MTC on a 4.1 source cluster, update the migration_controller and migration_ui parameters and add the deprecated_cors_configuration parameter to the migration_controller manifest:

    spec:
...
  migration_controller: false
  migration_ui: false
  deprecated_cors_configuration: true

    You do not need to update the manifest of the target cluster.

  7. Click Create.

  8. Click Workloads → Pods to verify that the MTC pods are running.

Upgrading MTC 1.3

If you are upgrading Migration Toolkit for Containers (MTC) version 1.3.x, you must manually update the indirectImageMigration and indirectVolumeMigration parameters in the MigPlan custom resource (CR).

Because the indirectImageMigration and indirectVolumeMigration parameters do not exist in version 1.3, their default value in version 1.4 is false, which means that direct image migration and direct volume migration are enabled. Because the direct migration requirements are not fulfilled, the migration plan cannot reach a Ready state unless these parameter values are changed to true.

Prerequisites

  • You must have upgraded MTC from version 1.3.x to 1.4.

  • You must have cluster-admin privileges.

Procedure

  1. Log in to the target cluster.

  2. Get the MigPlan CR:

    $ oc get migplan <migplan> -o yaml -n openshift-migration

  3. Change the following parameter values to true and save the file:

    ...
spec:
  indirectImageMigration: true
  indirectVolumeMigration: true

  4. Apply the changes:

    $ oc replace -f <migplan>.yaml -n openshift-migration

  5. Verify the changes by viewing the updated MigPlan CR:

    $ oc get migplan <migplan> -o yaml -n openshift-migration