You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/osd-create-cluster-ccs.adoc
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -220,6 +220,11 @@ CIDR configurations cannot be changed later. Confirm your selections with your n
220
220
You can review the end-of-life dates in the update life cycle documentation for {product-title}. For more information, see _{product-title} update life cycle_.
221
221
====
222
222
+
223
+
.. Provide administrator approval based on your cluster update method:
224
+
** Individual updates: If you select an update version that requires approval, provide an administrator’s acknowledgment and click *Approve and continue*.
225
+
** Recurring updates: If you selected recurring updates for your cluster, provide an administrator’s acknowledgment and click *Approve and continue*. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator’s acknowledgment.
226
+
+
227
+
For information about administrator acknowledgment, see xref:./../upgrading/osd-upgrading-cluster-prepare.adoc#upgrade-49-acknowledgement_osd-updating-cluster-prepare[Administrator acknowledgment when upgrading to OpenShift 4.9].
223
228
.. If you opted for recurring updates, select a preferred day of the week and upgrade start time in UTC from the drop-down menus.
224
229
.. Optional: You can set a grace period for *Node draining* during cluster upgrades. A *1 hour* grace period is set by default.
Copy file name to clipboardExpand all lines: modules/osd-create-cluster-red-hat-account.adoc
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,6 +105,11 @@ If the cluster privacy is set to *Private*, you cannot access your cluster until
105
105
You can review the end-of-life dates in the update life cycle documentation for {product-title}. For more information, see _{product-title} update life cycle_.
106
106
====
107
107
+
108
+
.. Provide administrator approval based on your cluster update method:
109
+
** Individual updates: If you select an update version that requires approval, provide an administrator’s acknowledgment and click *Approve and continue*.
110
+
** Recurring updates: If you selected recurring updates for your cluster, provide an administrator’s acknowledgment and click *Approve and continue*. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator’s acknowledgment.
111
+
+
112
+
For information about administrator acknowledgment, see xref:./../upgrading/osd-upgrading-cluster-prepare.adoc#upgrade-49-acknowledgement_osd-updating-cluster-prepare[Administrator acknowledgment when upgrading to OpenShift 4.9].
108
113
.. If you opted for recurring updates, select a preferred day of the week and upgrade start time in UTC from the drop-down menus.
109
114
.. Optional: You can set a grace period for *Node draining* during cluster upgrades. A *1 hour* grace period is set by default.
Copy file name to clipboardExpand all lines: modules/rosa-upgrading-automatic-ocm.adoc
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,16 +5,20 @@
5
5
6
6
:_content-type: PROCEDURE
7
7
[id="rosa-scheduling-upgrade_{context}"]
8
-
= Scheduling automatic upgrades
8
+
= Scheduling recurring upgrades for your cluster
9
9
10
-
You can schedule automatic upgrades for a {product-title} cluster through {cluster-manager-first} console.
10
+
You can schedule recurring, automatic upgrades for z-stream patch versions for your {product-title} cluster through the {cluster-manager} console.
11
11
12
12
.Procedure
13
13
14
14
. Log in to {cluster-manager-url}.
15
15
. Select a cluster to upgrade.
16
16
. Click the *Settings* tab.
17
-
. In the *Update strategy* pane, click *Automatic* and select a preferred day of the week and start time for the automatic upgrades.
17
+
. In the *Update strategy* pane, select *Recurring updates*.
18
+
. Select a preferred day of the week and start time for the upgrade, when updates are available.
19
+
. Provide an administrator’s acknowledgment and click *Approve and continue*. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator’s acknowledgment.
20
+
+
21
+
For information about administrator acknowledgment, see xref:./../upgrading/rosa-upgrading-cluster-prepare.adoc#upgrade-49-acknowledgement_rosa-updating-cluster-prepare[Administrator acknowledgment when upgrading to OpenShift 4.9].
18
22
. 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*.
19
23
. In the *Update strategy* pane, click *Save* to apply your update strategy.
Copy file name to clipboardExpand all lines: modules/rosa-upgrading-manual-ocm.adoc
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,13 +9,13 @@ endif::[]
9
9
10
10
:_content-type: PROCEDURE
11
11
[id="rosa-upgrade-ocm_{context}"]
12
-
= Upgrading using the console
12
+
= Scheduling individual upgrades through the{cluster-manager} console
13
13
14
-
You can upgrade a {product-title} cluster
14
+
You can schedule upgrades for a {product-title} cluster
15
15
ifdef::sts[]
16
16
that uses the AWS Security Token Service (STS)
17
17
endif::sts[]
18
-
manually by using {cluster-manager} console.
18
+
manually one time by using {cluster-manager} console.
19
19
20
20
ifdef::sts[]
21
21
.Prerequisites
@@ -28,7 +28,11 @@ endif::sts[]
28
28
. Log in to {cluster-manager-url}.
29
29
. Select a cluster to upgrade.
30
30
. Click the *Settings* tab.
31
-
. In the *Update strategy* pane, click *Manual* or *Individual Updates*.
31
+
. In the *Update strategy* pane, select *Individual Updates*.
32
+
. Select the version you want to upgrade your cluster to. Recommended cluster upgrades appear in the UI.
33
+
. If you select an update version that requires approval, provide an administrator’s acknowledgment and click *Approve and continue*.
34
+
+
35
+
For information about administrator acknowledgment, see xref:./../upgrading/rosa-upgrading-cluster-prepare.adoc#upgrade-49-acknowledgement_rosa-updating-cluster-prepare[Administrator acknowledgment when upgrading to OpenShift 4.9].
32
36
. 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*.
33
37
. In the *Update strategy* pane, click *Save* to apply your update strategy.
34
38
. In the *Update status* pane, review the *Update available* information and click *Update*.
Copy file name to clipboardExpand all lines: modules/upgrade-auto.adoc
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,27 +6,29 @@
6
6
:_content-type: PROCEDURE
7
7
[id="upgrade-auto_{context}"]
8
8
9
-
= Automatically upgrading your cluster through {cluster-manager-first}
9
+
= Scheduling recurring upgrades for your cluster
10
10
11
11
12
-
You can use {cluster-manager} to automatically upgrade your {product-title} cluster on a weekly basis. Based on upstream changes, there might be times when no updates are released. Therefore, no upgrade occurs for that week.
12
+
You can use {cluster-manager} to schedule recurring, automatic upgrades for z-stream patch versions for your {product-title} cluster. Based on upstream changes, there might be times when no updates are released. Therefore, no upgrade occurs for that week.
13
13
14
14
.Procedure
15
15
16
16
. From {console-red-hat}, select your cluster from the clusters list.
17
17
18
18
. Click the *Upgrade settings* tab to access the upgrade operator.
19
19
20
-
. To schedule automatic upgrades, select *Automatic*.
20
+
. To schedule recurring upgrades, select *Recurring updates*.
21
+
22
+
. Provide an administrator’s acknowledgment and click *Approve and continue*. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator’s acknowledgment.
21
23
22
24
. Specify the day of the week and the time you want your cluster to upgrade.
23
25
24
26
. Click *Save*.
25
27
26
28
. Optional: Set a grace period for *Node draining* by selecting a designated amount of time from the drop down list. A *1 hour* grace period is set by default.
27
29
28
-
. To edit an existing automatic upgrade policy, edit the preferred day or start time from the *Upgrade Settings* tab. Click *Save*.
30
+
. To edit an existing recurring upgrade policy, edit the preferred day or start time from the *Upgrade Settings* tab. Click *Save*.
29
31
30
-
. To cancel an automatic upgrade policy, switch the upgrade method to manual from the *Upgrade Settings* tab. Click *Save*.
32
+
. To cancel a recurring upgrade policy, switch the upgrade method to individual from the *Upgrade Settings* tab. Click *Save*.
31
33
32
34
On the *Upgrade settings* tab, the *Upgrade status* box indicates that an upgrade is scheduled. The date and time of the next scheduled update is listed.
Copy file name to clipboardExpand all lines: modules/upgrade-manual.adoc
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,10 +6,10 @@
6
6
:_content-type: PROCEDURE
7
7
[id="upgrade-manual_{context}"]
8
8
9
-
= Manually upgrading your cluster through {cluster-manager-first}
9
+
= Scheduling individual upgrades for your cluster
10
10
11
11
12
-
You can use {cluster-manager} to manually upgrade your {product-title} cluster.
12
+
You can use {cluster-manager} to manually upgrade your {product-title} cluster one time.
13
13
14
14
15
15
.Procedure
@@ -18,9 +18,14 @@ You can use {cluster-manager} to manually upgrade your {product-title} cluster.
18
18
19
19
. Click the *Upgrade settings* tab to access the upgrade operator. You can also update your cluster from the *Overview* tab by clicking *Update* next to the cluster version under the *Details* heading.
20
20
21
+
22
+
. To schedule an individual upgrade, select *Individual updates*.
23
+
21
24
. Click *Update* in the *Update Status* box.
22
25
23
-
. Select the version you want to upgrade your cluster to. Recommended cluster upgrades will be notated in the UI. To learn more about each available upgrade version, click *View release notes*.
26
+
. Select the version you want to upgrade your cluster to. Recommended cluster upgrades appear in the UI. To learn more about each available upgrade version, click *View release notes*.
27
+
28
+
. If you select an update version that requires approval, provide an administrator’s acknowledgment and click *Approve and continue*.
24
29
25
30
. Click *Next*.
26
31
@@ -42,5 +47,5 @@ The same upgrade details are available on the *Upgrade settings* tab under the *
42
47
43
48
[WARNING]
44
49
====
45
-
In the event that a CVE or other critical issue to OpenShift Dedicated is found, all clusters are upgraded within 48 hours of the fix being released. You are notified when the fix is available and informed that the cluster will be automatically upgraded at your latest preferred start time before the 48 hour window closes. You can also upgrade manually at any time before the automatic upgrade starts.
50
+
In the event that a CVE or other critical issue to {product-title} is found, all clusters are upgraded within 48 hours of the fix being released. You are notified when the fix is available and informed that the cluster will be automatically upgraded at your latest preferred start time before the 48 hour window closes. You can also upgrade manually at any time before the recurring upgrade starts.
Copy file name to clipboardExpand all lines: modules/upgrade.adoc
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,19 +20,23 @@ All Kubernetes objects and PVs in each {product-title} cluster are backed up as
20
20
====
21
21
22
22
[id="upgrade-automatic_{context}"]
23
-
== Automatic upgrades
23
+
== Recurring upgrades
24
24
25
25
Upgrades can be scheduled to occur automatically on a day and time specified by the cluster owner or administrator. Upgrades occur on a weekly basis, unless an upgrade is unavailable for that week.
26
26
27
+
If you select recurring updates for your cluster, you must provide an administrator’s acknowledgment. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator’s acknowledgment. For information about administrator acknowledgment, see link:https://docs.openshift.com/dedicated/upgrading/osd-upgrading-cluster-prepare.html#upgrade-49-acknowledgement_osd-updating-cluster-prepare[Administrator acknowledgment when upgrading to OpenShift 4.9].
28
+
27
29
[NOTE]
28
30
====
29
-
Automatic upgrade policies are optional and if they are not set, the upgrade policies default to manual.
31
+
Recurring upgrade policies are optional and if they are not set, the upgrade policies default to individual.
30
32
====
31
33
32
34
[id="upgrade-manual_upgrades_{context}"]
33
-
== Manual upgrades
35
+
== Individual upgrades
36
+
37
+
If you opt for individual upgrades, you are responsible for updating your cluster. If you select an update version that requires approval, you must provide an administrator’s acknowledgment. For information about administrator acknowledgment, see xref:./../upgrading/osd-upgrading-cluster-prepare.adoc#upgrade-49-acknowledgement_osd-updating-cluster-prepare[Administrator acknowledgment when upgrading to OpenShift 4.9].
34
38
35
-
If you opt for manual upgrades, you are responsible for updating your cluster. If your cluster version falls too far behind, it will transition to a limited support status. For more information on OpenShift life cycle policies, see xref:../osd_architecture/osd_policy/osd-life-cycle.adoc#osd-life-cycle[{product-title} update life cycle].
39
+
If your clusterversion becomes outdated, it will transition to a limited support status. For more information on OpenShift life cycle policies, see xref:../osd_architecture/osd_policy/osd-life-cycle.adoc#osd-life-cycle[{product-title} update life cycle].
36
40
37
41
[id="upgrade-notifications_{context}"]
38
42
== Upgrade notifications
@@ -48,7 +52,7 @@ Every change of state also triggers an email notification to the cluster owner a
48
52
49
53
[NOTE]
50
54
====
51
-
For automatic upgrades, you will also receive email notifications before the upgrade occurs based on the following cadence:
55
+
For recurring upgrades, you will also receive email notifications before the upgrade occurs based on the following cadence:
Copy file name to clipboardExpand all lines: upgrading/rosa-upgrading.adoc
+3-12Lines changed: 3 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,24 +15,15 @@ To plan an upgrade, review the xref:../rosa_architecture/rosa_policy_service_def
15
15
== Upgrading a ROSA cluster
16
16
There are three methods to upgrade {product-title} (ROSA) clusters:
17
17
18
-
* Manual upgrades through the `rosa` CLI
19
-
* Manual upgrades through the {cluster-manager} console
20
-
* Automatic upgrades through the {cluster-manager} console
21
-
22
-
Remove
18
+
* Individual upgrades through the `rosa` CLI
19
+
* Individual upgrades through the {cluster-manager-url} console
20
+
* Recurring upgrades through the {cluster-manager-url} console
23
21
24
22
[NOTE]
25
23
====
26
24
For steps to upgrade a ROSA cluster that uses the AWS Security Token Service (STS), see xref:../upgrading/rosa-upgrading-sts.adoc#rosa-upgrading-sts[Upgrading ROSA clusters with STS].
27
25
====
28
26
29
-
30
-
There are three methods to upgrade {product-title} (ROSA) clusters:
31
-
32
-
* Manual upgrades through the `rosa` CLI
33
-
* Manual upgrades through the {cluster-manager-url} console
34
-
* Automatic upgrades through the {cluster-manager-url} console
0 commit comments