mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
92 lines
3.1 KiB
Plaintext
92 lines
3.1 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * updating/updating_a_cluster/migrating-to-multi-payload.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="migrating-to-multi-arch-cli_{context}"]
|
|
= Migrating to a cluster with multi-architecture compute machines using the CLI
|
|
|
|
.Prerequisites
|
|
|
|
* You have access to the cluster as a user with the `cluster-admin` role.
|
|
* Your {product-title} version is up to date to at least version 4.13.0.
|
|
+
|
|
For more information on how to update your cluster version, see _Updating a cluster using the web console_ or _Updating a cluster using the CLI_.
|
|
* You have installed the OpenShift CLI (`oc`) that matches the version for your current cluster.
|
|
* Your `oc` client is updated to at least verion 4.13.0.
|
|
* Your {product-title} cluster is installed on AWS, Azure, {gcp-short}, bare metal or IBM P/Z platforms.
|
|
+
|
|
For more information on selecting a supported platform for your cluster installation, see _Selecting a cluster installation type_.
|
|
|
|
|
|
.Procedure
|
|
. Verify that the `RetrievedUpdates` condition is `True` in the Cluster Version Operator (CVO) by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get clusterversion/version -o=jsonpath="{.status.conditions[?(.type=='RetrievedUpdates')].status}"
|
|
----
|
|
+
|
|
If the `RetrievedUpates` condition is `False`, you can find supplemental information regarding the failure by using the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade
|
|
----
|
|
+
|
|
For more information about cluster version condition types, see _Understanding cluster version condition types_.
|
|
|
|
ifndef::openshift-origin[]
|
|
. If the condition `RetrievedUpdates` is `False`, change the channel to `stable-<4.y>` or `fast-<4.y>` with the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade channel <channel>
|
|
----
|
|
+
|
|
After setting the channel, verify if `RetrievedUpdates` is `True`.
|
|
+
|
|
For more information about channels, see _Understanding update channels and releases_.
|
|
endif::openshift-origin[]
|
|
|
|
. Migrate to the multi-architecture payload with following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade --to-multi-arch
|
|
----
|
|
|
|
.Verification
|
|
|
|
* You can monitor the migration by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade
|
|
----
|
|
+
|
|
.Example output
|
|
|
|
[source,terminal]
|
|
----
|
|
working towards ${VERSION}: 106 of 841 done (12% complete), waiting on machine-config
|
|
----
|
|
+
|
|
[IMPORTANT]
|
|
====
|
|
Machine launches may fail as the cluster settles into the new state. To notice and recover when machines fail to launch, we recommend deploying machine health checks. For more information about machine health checks and how to deploy them, see _About machine health checks_.
|
|
====
|
|
+
|
|
. Optional: To retrieve more detailed information about the status of your update, monitor the migration by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade status
|
|
----
|
|
+
|
|
For more information about how to use the `oc adm upgrade status` command, see _Gathering cluster update status using oc adm upgrade status (Technology Preview)_.
|
|
|
|
The migrations must be complete and all the cluster operators must be stable before you can add compute machine sets with different architectures to your cluster.
|
|
|
|
|