Este contenido no está disponible en el idioma seleccionado.
Chapter 6. Updating a cluster using the CLI
You can update, or upgrade, an OpenShift Container Platform cluster within a minor version by using the OpenShift CLI (
oc
6.1. Prerequisites Copiar enlaceEnlace copiado en el portapapeles!
-
Have access to the cluster as a user with privileges. See Using RBAC to define and apply permissions.
admin - Have a recent etcd backup in case your update fails and you must restore your cluster to a previous state.
- Ensure all Operators previously installed through Operator Lifecycle Manager (OLM) are updated to their latest version in their latest channel. Updating the Operators ensures they have a valid update path when the default OperatorHub catalogs switch from the current minor version to the next during a cluster update. See Updating installed Operators for more information.
- Ensure that all machine config pools (MCPs) are running and not paused. Nodes associated with a paused MCP are skipped during the update process. You can pause the MCPs if you are performing a canary rollout update strategy.
- If your cluster uses manually maintained credentials, ensure that the Cloud Credential Operator (CCO) is in an upgradeable state. For more information, see Upgrading clusters with manually maintained credentials for AWS, Azure, or GCP.
-
If you run an Operator or you have configured any application with the pod disruption budget, you might experience an interruption during the upgrade process. If is set to 1 in
minAvailable, the nodes are drained to apply pending machine configs which might block the eviction process. If several nodes are rebooted, all the pods might run on only one node, and thePodDisruptionBudgetfield can prevent the node drain.PodDisruptionBudget
- When an update is failing to complete, the Cluster Version Operator (CVO) reports the status of any blocking components while attempting to reconcile the update. Rolling your cluster back to a previous version is not supported. If your update is failing to complete, contact Red Hat support.
-
Using the section to modify the configuration of an Operator is unsupported and might block cluster updates. You must remove this setting before you can update your cluster.
unsupportedConfigOverrides
6.2. Updating a cluster by using the CLI Copiar enlaceEnlace copiado en el portapapeles!
If updates are available, you can update your cluster by using the OpenShift CLI (
oc
You can find information about available OpenShift Container Platform advisories and updates in the errata section of the Customer Portal.
Prerequisites
-
Install the OpenShift CLI () that matches the version for your updated version.
oc -
Log in to the cluster as user with privileges.
cluster-admin -
Install the package.
jq
Procedure
Ensure that your cluster is available:
$ oc get clusterversionExample output
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.9 True False 158m Cluster version is 4.6.9Review the current update channel information and confirm that your channel is set to
:stable-4.8$ oc get clusterversion -o json|jq ".items[0].spec"Example output
{ "channel": "stable-4.8", "clusterID": "990f7ab8-109b-4c95-8480-2bd1deec55ff" }ImportantFor production clusters, you must subscribe to a
orstable-*channel.fast-*View the available updates and note the version number of the update that you want to apply:
$ oc adm upgradeExample output
Cluster version is 4.1.0 Updates: VERSION IMAGE 4.1.2 quay.io/openshift-release-dev/ocp-release@sha256:9c5f0df8b192a0d7b46cd5f6a4da2289c155fd5302dec7954f8f06c878160b8bApply an update:
Review the status of the Cluster Version Operator:
$ oc get clusterversion -o json|jq ".items[0].spec"Example output
{ "channel": "stable-4.8", "clusterID": "990f7ab8-109b-4c95-8480-2bd1deec55ff", "desiredUpdate": { "force": false, "image": "quay.io/openshift-release-dev/ocp-release@sha256:9c5f0df8b192a0d7b46cd5f6a4da2289c155fd5302dec7954f8f06c878160b8b", "version": "4.8.0"1 } }- 1
- If the
versionnumber in thedesiredUpdatestanza matches the value that you specified, the update is in progress.
Review the cluster version status history to monitor the status of the update. It might take some time for all the objects to finish updating.
$ oc get clusterversion -o json|jq ".items[0].status.history"Example output
[ { "completionTime": null, "image": "quay.io/openshift-release-dev/ocp-release@sha256:b8fa13e09d869089fc5957c32b02b7d3792a0b6f36693432acc0409615ab23b7", "startedTime": "2021-01-28T20:30:50Z", "state": "Partial", "verified": true, "version": "4.8.0" }, { "completionTime": "2021-01-28T20:30:50Z", "image": "quay.io/openshift-release-dev/ocp-release@sha256:b8fa13e09d869089fc5957c32b02b7d3792a0b6f36693432acc0409615ab23b7", "startedTime": "2021-01-28T17:38:10Z", "state": "Completed", "verified": false, "version": "4.8.0" } ]The history contains a list of the most recent versions applied to the cluster. This value is updated when the CVO applies an update. The list is ordered by date, where the newest update is first in the list. Updates in the history have state
if the rollout completed andCompletedif the update failed or did not complete.PartialAfter the update completes, you can confirm that the cluster version has updated to the new version:
$ oc get clusterversionExample output
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0 True False 2m Cluster version is 4.8.0If you are upgrading your cluster to the next minor version, like version 4.y to 4.(y+1), it is recommended to confirm your nodes are upgraded before deploying workloads that rely on a new feature:
$ oc get nodesExample output
NAME STATUS ROLES AGE VERSION ip-10-0-168-251.ec2.internal Ready master 82m v1.21.0 ip-10-0-170-223.ec2.internal Ready master 82m v1.21.0 ip-10-0-179-95.ec2.internal Ready worker 70m v1.21.0 ip-10-0-182-134.ec2.internal Ready worker 70m v1.21.0 ip-10-0-211-16.ec2.internal Ready master 82m v1.21.0 ip-10-0-250-100.ec2.internal Ready worker 69m v1.21.0
6.3. Changing the update server by using the CLI Copiar enlaceEnlace copiado en el portapapeles!
Changing the update server is optional. If you have an OpenShift Update Service (OSUS) installed and configured locally, you must set the URL for the server as the
upstream
upstream
https://api.openshift.com/api/upgrades_info/v1/graph
Procedure
Change the
parameter value in the cluster version:upstream$ oc patch clusterversion/version --patch '{"spec":{"upstream":"<update-server-url>"}}' --type=mergeThe
variable specifies the URL for the update server.<update-server-url>Example output
clusterversion.config.openshift.io/version patched