This documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 6. Upgrading the Migration Toolkit for Containers
You can upgrade the Migration Toolkit for Containers (MTC) by using the OpenShift Container Platform web console.
You must ensure that you upgrade to the same MTC version on all clusters.
If you are upgrading from MTC version 1.3, you must perform an additional procedure to update the MigPlan
custom resource (CR).
6.1. Upgrading the Migration Toolkit for Containers on OpenShift Container Platform 4 Link kopierenLink in die Zwischenablage kopiert!
You can upgrade the Migration Toolkit for Containers (MTC) on OpenShift Container Platform 4 by using the OpenShift Container Platform web console.
Prerequisites
-
You must be logged in as a user with
cluster-admin
privileges.
Procedure
In the OpenShift Container Platform console, navigate to Operators
Installed Operators. Operators that have a pending upgrade display an Upgrade available status.
- Click Migration Toolkit for Containers Operator.
- Click the Subscription tab. Any upgrades requiring approval are displayed next to Upgrade Status. For example, it might display 1 requires approval.
- Click 1 requires approval, then click Preview Install Plan.
- Review the resources that are listed as available for upgrade and click Approve.
-
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. -
Click Workloads
Pods to verify that the MTC pods are running.
6.2. Upgrading the Migration Toolkit for Containers on OpenShift Container Platform 3 Link kopierenLink in die Zwischenablage kopiert!
You can upgrade Migration Toolkit for Containers (MTC) on OpenShift Container Platform 3 with podman
.
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
Log in to
registry.redhat.io
with your Red Hat Customer Portal credentials:sudo podman login registry.redhat.io
$ sudo podman login registry.redhat.io
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Download the latest
operator.yml
file:sudo podman cp $(sudo podman create \ registry.redhat.io/rhmtc/openshift-migration-rhel7-operator:v1.4):/operator.yml ./
$ sudo podman cp $(sudo podman create \ registry.redhat.io/rhmtc/openshift-migration-rhel7-operator:v1.4):/operator.yml ./
1 Copy to Clipboard Copied! Toggle word wrap Toggle overflow - 1
- You can specify a z-stream release, if necessary.
Replace the Migration Toolkit for Containers Operator:
oc replace --force -f operator.yml
$ oc replace --force -f operator.yml
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Apply the changes:
For MTC 1.1.2 and earlier versions, delete the
Restic
pods:oc delete pod <restic_pod>
$ oc delete pod <restic_pod>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow For MTC 1.2 and later versions:
Scale the
migration-operator
deployment to0
to stop the deployment:oc scale -n openshift-migration --replicas=0 deployment/migration-operator
$ oc scale -n openshift-migration --replicas=0 deployment/migration-operator
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Scale the
migration-operator
deployment to1
to start the deployment and apply the changes:oc scale -n openshift-migration --replicas=1 deployment/migration-operator
$ oc scale -n openshift-migration --replicas=1 deployment/migration-operator
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Verify that the
migration-operator
was upgraded:oc -o yaml -n openshift-migration get deployment/migration-operator | grep image: | awk -F ":" '{ print $NF }'
$ oc -o yaml -n openshift-migration get deployment/migration-operator | grep image: | awk -F ":" '{ print $NF }'
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Download the latest
controller-3.yml
file:sudo podman cp $(sudo podman create \ registry.redhat.io/rhmtc/openshift-migration-rhel7-operator:v1.4):/controller-3.yml ./
$ sudo podman cp $(sudo podman create \ registry.redhat.io/rhmtc/openshift-migration-rhel7-operator:v1.4):/controller-3.yml ./
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create the
migration-controller
object:oc create -f controller-3.yml
$ oc create -f controller-3.yml
Copy to Clipboard Copied! Toggle word wrap Toggle overflow If your OpenShift Container Platform version is 3.10 or earlier, set the security context constraint of the
migration-controller
service account toanyuid
to enable direct image migration and direct volume migration:oc adm policy add-scc-to-user anyuid -z migration-controller -n openshift-migration
$ oc adm policy add-scc-to-user anyuid -z migration-controller -n openshift-migration
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Verify that the MTC pods are running:
oc get pods -n openshift-migration
$ oc get pods -n openshift-migration
Copy to Clipboard Copied! Toggle word wrap Toggle overflow If you have previously added the OpenShift Container Platform 3 cluster to the MTC web console, you must update the service account token in the web console because the upgrade process deletes and restores the
openshift-migration
namespace:Obtain the service account token:
oc sa get-token migration-controller -n openshift-migration
$ oc sa get-token migration-controller -n openshift-migration
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - In the MTC web console, click Clusters.
-
Click the Options menu
next to the cluster and select Edit.
- Enter the new service account token in the Service account token field.
- Click Update cluster and then click Close.
6.3. Upgrading MTC 1.3 to 1.4 Link kopierenLink in die Zwischenablage kopiert!
If you are upgrading Migration Toolkit for Containers (MTC) version 1.3.x to 1.4, 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 have MTC 1.3 installed.
-
You must be logged in as a user with
cluster-admin
privileges.
Procedure
-
Log in to the cluster on which the
MigrationController
pod is running. Get the
MigPlan
CR manifest:oc get migplan <migplan> -o yaml -n openshift-migration
$ oc get migplan <migplan> -o yaml -n openshift-migration
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Update the following parameter values and save the file as
migplan.yaml
:... spec: indirectImageMigration: true indirectVolumeMigration: true
... spec: indirectImageMigration: true indirectVolumeMigration: true
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Replace the
MigPlan
CR manifest to apply the changes:oc replace -f migplan.yaml -n openshift-migration
$ oc replace -f migplan.yaml -n openshift-migration
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Get the updated
MigPlan
CR manifest to verify the changes:oc get migplan <migplan> -o yaml -n openshift-migration
$ oc get migplan <migplan> -o yaml -n openshift-migration
Copy to Clipboard Copied! Toggle word wrap Toggle overflow