Lifecycle policies and planning

To plan an upgrade, review the lifecycle policies. This information includes how many versions are supported, the CVE process, mandatory upgrade policies, and so on.

Upgrading a cluster

There are three methods to upgrade a Red Hat OpenShift Service on AWS (ROSA) cluster:

  • Manually through the rosa CLI

  • Manually through the OpenShift Cluster Manager (OCM) console

  • Scheduling automatic upgrades through the OpenShift Cluster Manager (OCM) console

Upgrading with the rosa CLI

There are three methods that can be used to upgrade Red Hat OpenShift Service on AWS clusters. This procedure describes upgrading using the rosa CLI.

This method schedules the cluster for an immediate upgrade, if a more recent version is available.

Procedure
  1. To verify the current version of your cluster, enter the following command:

    $ rosa describe cluster
  2. To verify that an upgrade is available, enter the following command:

    $ rosa list upgrade --cluster=<cluster_name>

    The command returns a list of versions to which the the cluster can be upgraded, including a recommended version.

  3. To upgrade a cluster to the latest available version, enter the following command:

    $ rosa upgrade cluster --cluster=<cluster_name>

    The cluster is scheduled for an immediate upgrade. This action can take an hour or longer, depending on your workload configuration, such as PodDisruptionBudgets.

    You will receive an email when the upgrade is complete. You can also check the status by running rosa describe cluster again from the rosa CLI or view the status in the OpenShift Cluster Manager (OCM) console.

Upgrading manually using the console

There are three methods that can be used to upgrade Red Hat OpenShift Service on AWS clusters. This procedure describes manually upgrading using the OpenShift Cluster Manager (OCM) console.

Procedure
  1. Log in to the OCM console.

  2. Select a cluster to upgrade.

  3. Click the Update settings tab.

  4. In the Update Strategy pane, click Manual.

    The scheduling options are displayed.

  5. Select the day of the week and the time for upgrades to occur.

  6. In the Node draining pane, select a grace period interval from the drop-down list to allow the nodes to gracefully drain before forcing the pod eviction. Default: 1 hour

  7. In the Update Status pane, review the Update available information.

  8. Click Update. This button is enabled only when an upgrade is available.

    The cluster is scheduled for an immediate upgrade to the latest version. This action can take an hour or longer, depending on your workload configuration, such as PodDisruptionBudgets.

    The status is displayed in the Update Status pane.

Scheduling automatic upgrades

There are three methods that can be used to upgrade Red Hat OpenShift Service on AWS clusters. This procedure describes scheduling automatic upgrades.

Procedure
  1. Log in to the OCM console.

  2. Select a cluster to upgrade.

  3. Click the Update settings tab.

  4. In the Update Strategy pane, click Automatic.

    The scheduling options are displayed.

  5. Select the day of the week and the time for upgrades to occur.

  6. In the Node draining pane, select a grace period interval from the drop-down list to allow the nodes to gracefully drain before forcing the pod eviction. Default: 1 hour

  7. Click Save.

    When upgrades are available, they are automatically applied to the cluster at the specified day of the week and time.