|
| 1 | +:_mod-docs-content-type: ASSEMBLY |
| 2 | +[id="cloud-experts-getting-started-upgrading"] |
| 3 | += Tutorial: Upgrading your cluster |
| 4 | +include::_attributes/attributes-openshift-dedicated.adoc[] |
| 5 | +:context: cloud-experts-getting-started-upgrading |
| 6 | + |
| 7 | +toc::[] |
| 8 | + |
| 9 | +//rosaworkshop.io content metadata |
| 10 | +//Brought into ROSA product docs 2024-01-08 |
| 11 | + |
| 12 | +{product-title} (ROSA) executes all cluster upgrades as part of the managed service. You do not need to run any commands or make changes to the cluster. You can schedule the upgrades at a convenient time. |
| 13 | + |
| 14 | +Ways to schedule a cluster upgrade include: |
| 15 | + |
| 16 | +* *Manually using the command line interface (CLI)*: Start a one-time immediate upgrade or schedule a one-time upgrade for a future date and time. |
| 17 | +* *Manually using the Red Hat OpenShift Cluster Manager user interface (UI)*: Start a one-time immediate upgrade or schedule a one-time upgrade for a future date and time. |
| 18 | +* *Automated upgrades*: Set an upgrade window for recurring y-stream upgrades whenever a new version is available without needing to manually schedule it. Minor versions have to be manually scheduled. |
| 19 | +
|
| 20 | +For more details about cluster upgrades, run the following command: |
| 21 | + |
| 22 | +[source,terminal] |
| 23 | +---- |
| 24 | +$ rosa upgrade cluster --help |
| 25 | +---- |
| 26 | + |
| 27 | +== Manually upgrading your cluster using the CLI |
| 28 | +. Check if there is an upgrade available by running the following command: |
| 29 | ++ |
| 30 | +[source,terminal] |
| 31 | +---- |
| 32 | +$ rosa list upgrade -c <cluster-name> |
| 33 | +---- |
| 34 | ++ |
| 35 | +.Example output |
| 36 | ++ |
| 37 | +[source,terminal] |
| 38 | +---- |
| 39 | +$ rosa list upgrade -c <cluster-name> |
| 40 | +VERSION NOTES |
| 41 | +4.14.7 recommended |
| 42 | +4.14.6 |
| 43 | +... |
| 44 | +---- |
| 45 | ++ |
| 46 | +In the above example, versions 4.14.7 and 4.14.6 are both available. |
| 47 | + |
| 48 | +. Schedule the cluster to upgrade within the hour by running the following command: |
| 49 | ++ |
| 50 | +[source,terminal] |
| 51 | +---- |
| 52 | +$ rosa upgrade cluster -c <cluster-name> --version <desired-version> |
| 53 | +---- |
| 54 | + |
| 55 | +. *Optional:* Schedule the cluster to upgrade at a later date and time by running the following command: |
| 56 | ++ |
| 57 | +[source,terminal] |
| 58 | +---- |
| 59 | +$ rosa upgrade cluster -c <cluster-name> --version <desired-version> --schedule-date <future-date-for-update> --schedule-time <future-time-for-update> |
| 60 | +---- |
| 61 | + |
| 62 | +== Manually upgrading your cluster using the UI |
| 63 | +. Log in to the OpenShift Cluster Manager, and select the cluster you want to upgrade. |
| 64 | +. Click *Settings*. |
| 65 | +. If an upgrade is available, click *Update*. |
| 66 | ++ |
| 67 | +image::cloud-experts-getting-started-cluster-upgrade.png[] |
| 68 | + |
| 69 | +. Select the version to which you want to upgrade in the new window. |
| 70 | +. Schedule a time for the upgrade or begin it immediately. |
| 71 | + |
| 72 | +== Setting up automatic recurring upgrades |
| 73 | +. Log in to the OpenShift Cluster Manager, and select the cluster you want to upgrade. |
| 74 | +. Click *Settings*. |
| 75 | +1. Under *Update Strategy*, click *Recurring updates*. |
| 76 | +. Set the day and time for the upgrade to occur. |
| 77 | +. Under *Node draining*, select a grace period to allow the nodes to drain before pod eviction. |
| 78 | +. Click *Save*. |
0 commit comments