Chapter 5. Upgrading the Migration Toolkit for Containers

Procedure

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

   Operators that have a pending upgrade display an Upgrade available status.

2. Click Migration Toolkit for Containers Operator.
3. Click the Subscription tab. Any upgrades requiring approval are displayed next to Upgrade Status. For example, it might display 1 requires approval.
4. Click 1 requires approval, then click Preview Install Plan.
5. Review the resources that are listed as available for upgrade and click Approve.
6. Navigate back to the Operators Installed Operators page to monitor the progress of the upgrade. When complete, the status changes to Succeeded and Up to date.
7. Click Workloads Pods to verify that the MTC pods are running.

Procedure

1. Determine subscription names and current channels to work with for upgrading by using one of the following methods:

   • Determine the subscription names and channels by running the following command:

     $ oc -n openshift-migration get sub

     Example output

     NAME                                                                         PACKAGE                SOURCE                 CHANNEL
     mtc-operator                                                                 mtc-operator           mtc-operator-catalog   release-v1.7
     redhat-oadp-operator-stable-1.0-mtc-operator-catalog-openshift-marketplace   redhat-oadp-operator   mtc-operator-catalog   stable-1.0

   • Or return the subscription names and channels in JSON by running the following command:

     $ oc -n openshift-migration get sub -o json | jq -r '.items[] | { name: .metadata.name, package: .spec.name, channel: .spec.channel }'

     Example output

     {
       "name": "mtc-operator",
       "package": "mtc-operator",
       "channel": "release-v1.7"
     }
     {
       "name": "redhat-oadp-operator-stable-1.0-mtc-operator-catalog-openshift-marketplace",
       "package": "redhat-oadp-operator",
       "channel": "stable-1.0"
     }

2. For each subscription, patch to move from the MTC 1.7 channel to the MTC 1.8 channel by running the following command:

   $ oc -n openshift-migration patch subscription mtc-operator --type merge --patch '{"spec": {"channel": "release-v1.8"}}'

   Example output

   subscription.operators.coreos.com/mtc-operator patched

Procedure

1. Log in to

   registry.redhat.io

   with your Red Hat Customer Portal credentials by entering the following command:

   $ podman login registry.redhat.io

2. Download the

   operator.yml

   file by entering the following command:

   $ podman cp $(podman create registry.redhat.io/rhmtc/openshift-migration-legacy-rhel8-operator:v1.7:/operator.yml ./

3. Replace the Migration Toolkit for Containers Operator by entering the following command:

   $ oc replace --force -f operator.yml

4. Scale the

   migration-operator

   deployment to

   0

   to stop the deployment by entering the following command:

   $ oc scale -n openshift-migration --replicas=0 deployment/migration-operator

5. Scale the

   migration-operator

   deployment to

   1

   to start the deployment and apply the changes by entering the following command:

   $ oc scale -n openshift-migration --replicas=1 deployment/migration-operator

6. Verify that the

   migration-operator

   was upgraded by entering the following command:

   $ oc -o yaml -n openshift-migration get deployment/migration-operator | grep image: | awk -F ":" '{ print $NF }'

7. Download the

   controller.yml

   file by entering the following command:

   $ podman cp $(podman create registry.redhat.io/rhmtc/openshift-migration-legacy-rhel8-operator:v1.7):/operator.yml ./

8. Create the

   migration-controller

   object by entering the following command:

   $ oc create -f controller.yml

9. Verify that the MTC pods are running by entering the following command:

   $ oc get pods -n openshift-migration

Procedure

1. Log in to the cluster on which the

   MigrationController

   pod is running.

2. Get the

   MigPlan

   CR manifest:

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

3. Update the following parameter values and save the file as

   migplan.yaml

   :

   ...
   spec:
     indirectImageMigration: true
     indirectVolumeMigration: true

4. Replace the

   MigPlan

   CR manifest to apply the changes:

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

5. Get the updated

   MigPlan

   CR manifest to verify the changes:

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