Este contenido no está disponible en el idioma seleccionado.

Chapter 5. Upgrading the Migration Toolkit for Containers


You can upgrade the Migration Toolkit for Containers (MTC) on OpenShift Container Platform 4.8 by using Operator Lifecycle Manager.

You can upgrade MTC on OpenShift Container Platform 4.5, and earlier versions, by reinstalling the legacy Migration Toolkit for Containers Operator.

Important

If you are upgrading from MTC version 1.3, you must perform an additional procedure to update the

MigPlan
custom resource (CR).

You can upgrade the Migration Toolkit for Containers (MTC) on OpenShift Container Platform 4.8 by using the Operator Lifecycle Manager.

Prerequisites

  • You must be logged in as a user with
    cluster-admin
    privileges.

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.

You can upgrade Migration Toolkit for Containers (MTC) on OpenShift Container Platform versions 4.2 to 4.5 by manually installing the legacy Migration Toolkit for Containers Operator.

Prerequisites

  • You must be logged in as a user with
    cluster-admin
    privileges.
  • You must have access to
    registry.redhat.io
    .
  • You must have
    podman
    installed.

Procedure

  1. Log in to

    registry.redhat.io
    with your Red Hat Customer Portal credentials by entering the following command:

    $ sudo podman login registry.redhat.io

Download the operator.yml file by entering the following command:

+

$ sudo podman cp $(sudo podman create \
  registry.redhat.io/rhmtc/openshift-migration-legacy-rhel8-operator:v1.7):/operator.yml ./
  1. Replace the Migration Toolkit for Containers Operator by entering the following command:

    $ oc replace --force -f operator.yml
  2. 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
  3. 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
  4. 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 }'
  5. Download the

    controller.yml
    file by entering the following command:

    $ sudo podman cp $(sudo podman create \
      registry.redhat.io/rhmtc/openshift-migration-legacy-rhel8-operator:v1.7):/controller.yml ./
  6. Create the

    migration-controller
    object by entering the following command:

    $ oc create -f controller.yml
  7. Verify that the MTC pods are running by entering the following command:

    $ oc get pods -n openshift-migration

5.3. Upgrading MTC 1.3 to 1.7

If you are upgrading Migration Toolkit for Containers (MTC) version 1.3.x to 1.7, you must update the

MigPlan
custom resource (CR) manifest on the cluster on which the
MigrationController
pod is running.

Because the

indirectImageMigration
and
indirectVolumeMigration
parameters do not exist in MTC 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 be logged in as a user with
    cluster-admin
    privileges.

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
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2026 Red Hat
Volver arriba