1. Documentation
    2. history bug_report picture_as_pdf
×

Upgrading ROSA clusters with STS

edit
edit

Life cycle policies and planning

To plan an upgrade, review the Red Hat OpenShift Service on AWS update life cycle. The life cycle page includes release definitions, support and upgrade requirements, installation policy information and life cycle dates.

Upgrades are manually initiated or automatically scheduled. Red Hat Site Reliability Engineers (SREs) monitor upgrade progress and remedy any issues encountered.

Upgrading a ROSA cluster that uses STS

There are two methods to upgrade Red Hat OpenShift Service on AWS (ROSA) clusters that uses the AWS Security Token Service (STS):

  • Individual upgrades through the ROSA CLI (rosa)

  • Individual upgrades through the OpenShift Cluster Manager console

For steps to upgrade a ROSA cluster that does not use the AWS Security Token Service (STS), see Upgrading ROSA clusters.
edit

Upgrading with the ROSA CLI

You can upgrade a Red Hat OpenShift Service on AWS (ROSA) cluster that uses the AWS Security Token Service (STS) manually by using the ROSA CLI (rosa).

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

Prerequisites

  • You have installed and configured the latest ROSA CLI on your installation host.

Procedure

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

    $ rosa describe cluster --cluster=<cluster_name|cluster_id> (1)
    1 Replace <cluster_name|cluster_id> with the cluster name or the ID of the cluster.

  2. To verify that an upgrade is available, enter the following command:

    $ rosa list upgrade --cluster=<cluster_name|cluster_id>

    The command returns a list of versions to which 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|cluster_id>

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

    You will receive an email when the upgrade is complete. You can also check the status by running the rosa describe cluster command again from the ROSA CLI or view the status in OpenShift Cluster Manager console. :!sts:

Troubleshooting
edit

Scheduling individual upgrades through the OpenShift Cluster Manager console

You can schedule upgrades for a Red Hat OpenShift Service on AWS cluster that uses the AWS Security Token Service (STS) manually one time by using OpenShift Cluster Manager console.

Procedure

  1. Log in to OpenShift Cluster Manager.

  2. Select a cluster to upgrade.

  3. Click the Settings tab.

  4. In the Update strategy pane, select Individual Updates.

  5. Select the version you want to upgrade your cluster to. Recommended cluster upgrades appear in the UI.

  6. If you select an update version that requires approval, provide an administrator’s acknowledgment and click Approve and continue.

  7. In the Node draining pane, select a grace period interval from the list. The grace period enables the nodes to gracefully drain before forcing the pod eviction. The default is 1 hour.

    You cannot change the node drain grace period after you start the upgrade process.

  8. In the Update strategy pane, click Save to apply your update strategy.

  9. In the Update status pane, review the Update available information and click Update.

    The Update button is enabled only when an upgrade is available.

  10. In the Select version dialog, choose a target upgrade version and click Next.

  11. In the Schedule update dialog, schedule your cluster upgrade.

    • To upgrade within an hour, select Update now and click Next.

    • To upgrade at a later time, select Schedule a different time and set a time and date for your upgrade. Click Next to proceed to the confirmation dialog.

  12. After reviewing the version and schedule summary, select Confirm update.

    The cluster is scheduled for an upgrade to the target version. This action can take an hour or longer, depending on the selected upgrade schedule and your workload configuration, such as pod disruption budgets.

    The status is displayed in the Update status pane.

Troubleshooting