JIRA-OSDOCS3322: Updated the steps for cluster upgrades per the UI changes #44907

sayjadha · 2022-04-23T00:12:14Z

This PR is to address the JIRA issue: https://issues.redhat.com/browse/OSDOCS-3322

Following is the change:
Per the latest UI changes, made the following updates to the cluster upgrade content:

Changed 'manual upgrades' to 'individual upgrades' in conceptual info. and procedures for both OSD and ROSA docs.
Changed 'automatic upgrades' to 'recurring upgrades' in conceptual info. and procedures for both OSD and ROSA docs.
Wireframe: https://marvelapp.com/prototype/hdh8ai1/screen/84703875

The change is seen in the following topics:
OSD topics:

http://file.rdu.redhat.com/sayjadha/JIRA-OSDOCS3322/osd_cluster_create/creating-an-aws-cluster.html (Procedure 'Creating a cluster on AWS with CCS' > Updated step 16 + added substep b.). The same update is seen in procedure 'Creating a cluster on AWS with a Red Hat cloud account' > Updated step 11 + added substep b.
http://file.rdu.redhat.com/sayjadha/JIRA-OSDOCS3322/osd_cluster_create/creating-a-gcp-cluster.html (Creating a cluster on AWS with CCS > Updated step 16, added substep b.) The same update is seen in procedure 'Creating a cluster on AWS with a Red Hat cloud account' > Updated step 11 + added substep b.
http://file.rdu.redhat.com/sayjadha/JIRA-OSDOCS3322/upgrading/osd-upgrades.html (1: Updated sections 'Recurring updates' and 'Individual updates'. 2: Updated title to 'Scheduling recurring upgrades for your cluster' and updated the procedure per UI updates. 3: Updated title to 'Scheduling individual upgrades for your cluster' and updated the procedure per UI updates.)

ROSA topics:

http://file.rdu.redhat.com/sayjadha/JIRA-OSDOCS3322/upgrading/rosa-upgrading-cluster-prepare.html (For an unknown reason, this topic was not referenced correctly in the topic.yml file for ROSA and thus wasn't published. Updated the reference now.)
http://file.rdu.redhat.com/sayjadha/JIRA-OSDOCS3322/upgrading/rosa-upgrading-sts.html (1: Updated title to 'Scheduling individual upgrades through the OpenShift Cluster Manager console'. 2: Updated the procedure per UI updates)
http://file.rdu.redhat.com/sayjadha/JIRA-OSDOCS3322/upgrading/rosa-upgrading.html (1: Updated titles to 'Scheduling individual upgrades through the OpenShift Cluster Manager console' and 'Scheduling recurring upgrades for your cluster'. 2: Updated the introduction and procedures per UI updates)

Repo: Request cherrypick to enterprise-4.10 and enterprise-4.11

netlify · 2022-04-23T00:14:29Z

✅ Deploy Preview for osdocs ready!

Name	Link
🔨 Latest commit	3d7ac7dac0ab9ee549a245ceec0240a10f4bba34
🔍 Latest deploy log	https://app.netlify.com/sites/osdocs/deploys/6281d816368afd000873f1d4
😎 Deploy Preview	https://deploy-preview-44907--osdocs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

wgordon17

Added additional context that admin requirement is only for y-stream versions, while the z-stream versions continue to happen automatically

modules/osd-create-cluster-ccs.adoc

modules/osd-create-cluster-red-hat-account.adoc

modules/rosa-upgrading-automatic-ocm.adoc

modules/upgrade-auto.adoc

modules/upgrade.adoc

arendej

Reviewed the ROSA pages.

xueli181114 · 2022-05-10T06:18:01Z

modules/osd-create-cluster-red-hat-account.adoc

@@ -105,6 +105,11 @@ If the cluster privacy is set to *Private*, you cannot access your cluster until
 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_.
 ====
 +
+.. Provide administrator approval per your cluster update method:
+** Individual updates: If you select an update version that requires approval, provide an administrator’s acknowledgment and click *Approve and continue*.
+** Recurring updates: If you selected recurring updates for your cluster, provide an administrator’s acknowledgment and click *Approve and continue*. The {cluster-manager} does not start scheduled updates without receiving an administrator's acknowledgment.


y-stream upgrade is controlled by another attribute enable_minor_version_upgrades set to true which is not supported on UI yet.

modules/upgrade.adoc

EricPonvelle

/lgtm

xueli181114 · 2022-05-11T01:30:42Z

/lgtm

modules/rosa-upgrading-automatic-ocm.adoc

Tessg22

Suggested small text corrections.

modules/rosa-upgrading-manual-ocm.adoc

modules/upgrade-manual.adoc

openshift-ci · 2022-05-12T16:11:15Z

New changes are detected. LGTM label has been removed.

sayjadha · 2022-05-12T17:02:26Z

@wgordon17 , @xueli181114 : I incorporated your feedback. Could you please review the doc updates and let me know if you have any additional comments? Thank you.

wgordon17

LGTM

modules/osd-create-cluster-ccs.adoc

lpettyjo

Otherwise, LGTM!

lpettyjo · 2022-06-17T12:43:42Z

modules/rosa-upgrading-manual-ocm.adoc

@@ -28,7 +28,11 @@ endif::sts[]
 . Log in to {cluster-manager-url}.
 . Select a cluster to upgrade.
 . Click the *Settings* tab.
-. In the *Update strategy* pane, click *Manual* or *Individual Updates*.
+. In the *Update strategy* pane, select *Individual Updates*.
+. Select the version you want to upgrade your cluster to. Recommended cluster upgrades are notated in the UI.


Recommend changing to "Recommended cluster upgrades appear in the UI." for simpler language.

Made the change.

lpettyjo · 2022-06-17T12:45:30Z

modules/upgrade-manual.adoc

 . Click *Update* in the *Update Status* box.

-. 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*.
+. Select the version you want to upgrade your cluster to. Recommended cluster upgrades are notated in the UI. To learn more about each available upgrade version, click *View release notes*.


Same comment as above.

Incorporated the feedback.

lpettyjo · 2022-06-17T12:51:16Z

modules/upgrade.adoc


-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_policy/osd-life-cycle.adoc#osd-life-cycle[{product-title} update life cycle].
+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].


Change "fall too far behind" to "becomes outdated"?

Made the change.

and incorporated tech. and peer feedback

maxwelldb · 2022-06-21T20:10:10Z

/cherry-pick enterprise-4.10

maxwelldb · 2022-06-21T20:10:17Z

/cherry-pick enterprise-4.11

openshift-cherrypick-robot · 2022-06-21T20:10:53Z

@maxwelldb: new pull request created: #46906

In response to this:

/cherry-pick enterprise-4.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

openshift-cherrypick-robot · 2022-06-21T20:10:59Z

@maxwelldb: new pull request created: #46907

In response to this:

/cherry-pick enterprise-4.11

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 23, 2022

sayjadha force-pushed the JIRA-OSDOCS3322 branch from 3ec85aa to 7c00561 Compare April 23, 2022 00:26

sayjadha force-pushed the JIRA-OSDOCS3322 branch from 7c00561 to e03d55f Compare May 9, 2022 02:20

openshift-ci bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels May 9, 2022

sayjadha force-pushed the JIRA-OSDOCS3322 branch 2 times, most recently from c587557 to 6778d1c Compare May 9, 2022 16:33

wgordon17 requested changes May 9, 2022

View reviewed changes

arendej approved these changes May 9, 2022

View reviewed changes

xueli181114 reviewed May 10, 2022

View reviewed changes

modules/upgrade.adoc Outdated Show resolved Hide resolved

EricPonvelle added branch/enterprise-4.9 branch/enterprise-4.10 branch/enterprise-4.11 labels May 10, 2022

EricPonvelle added this to the Next Release milestone May 10, 2022

EricPonvelle reviewed May 10, 2022

View reviewed changes

openshift-ci bot assigned EricPonvelle May 10, 2022

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 10, 2022

openshift-ci bot assigned xueli181114 May 11, 2022

Tessg22 reviewed May 11, 2022

View reviewed changes

modules/rosa-upgrading-automatic-ocm.adoc Show resolved Hide resolved

Tessg22 reviewed May 11, 2022

View reviewed changes

modules/rosa-upgrading-manual-ocm.adoc Show resolved Hide resolved

modules/upgrade-manual.adoc Outdated Show resolved Hide resolved

sayjadha force-pushed the JIRA-OSDOCS3322 branch from 6778d1c to 484ab16 Compare May 12, 2022 16:10

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 12, 2022

wgordon17 approved these changes May 12, 2022

View reviewed changes

sayjadha force-pushed the JIRA-OSDOCS3322 branch from 484ab16 to 0adb1ce Compare May 12, 2022 18:42

mburke5678 reviewed May 12, 2022

View reviewed changes

modules/osd-create-cluster-ccs.adoc Outdated Show resolved Hide resolved

sayjadha force-pushed the JIRA-OSDOCS3322 branch from 3d7ac7d to baac340 Compare May 25, 2022 15:05

openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 25, 2022

sayjadha force-pushed the JIRA-OSDOCS3322 branch from baac340 to 1c637b8 Compare May 25, 2022 15:47

openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 25, 2022

sayjadha force-pushed the JIRA-OSDOCS3322 branch from 1c637b8 to 8a863d9 Compare May 25, 2022 15:59

openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 25, 2022

sayjadha force-pushed the JIRA-OSDOCS3322 branch from 8a863d9 to b05060d Compare May 25, 2022 16:12

openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 25, 2022

sayjadha force-pushed the JIRA-OSDOCS3322 branch from b05060d to 16e4d60 Compare June 1, 2022 12:30

openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 1, 2022

lpettyjo added the peer-review-needed Signifies that the peer review team needs to review this PR label Jun 17, 2022

lpettyjo self-requested a review June 17, 2022 12:37

lpettyjo reviewed Jun 17, 2022

View reviewed changes

lpettyjo added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Jun 17, 2022

sayjadha force-pushed the JIRA-OSDOCS3322 branch from 16e4d60 to 031adb3 Compare June 21, 2022 11:34

openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 21, 2022

sayjadha force-pushed the JIRA-OSDOCS3322 branch from 031adb3 to 5bd779b Compare June 21, 2022 11:44

JIRA-OSDOCS3322: Updated the cluster upgrade content per the UI changes

60a20ca

and incorporated tech. and peer feedback

sayjadha force-pushed the JIRA-OSDOCS3322 branch from 5bd779b to 60a20ca Compare June 21, 2022 19:51

openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 21, 2022

maxwelldb removed the branch/enterprise-4.9 label Jun 21, 2022

maxwelldb merged commit 614fbc9 into openshift:main Jun 21, 2022

openshift-cherrypick-robot mentioned this pull request Jun 21, 2022

[enterprise-4.10] JIRA-OSDOCS3322: Updated the steps for cluster upgrades per the UI changes #46906

Merged

openshift-cherrypick-robot mentioned this pull request Jun 21, 2022

[enterprise-4.11] JIRA-OSDOCS3322: Updated the steps for cluster upgrades per the UI changes #46907

Merged

skopacz1 mentioned this pull request Nov 9, 2022

[online] Issue in file upgrading/rosa-upgrading.adoc #52546

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

JIRA-OSDOCS3322: Updated the steps for cluster upgrades per the UI changes #44907

JIRA-OSDOCS3322: Updated the steps for cluster upgrades per the UI changes #44907

sayjadha commented Apr 23, 2022 •

edited

Loading

netlify bot commented Apr 23, 2022 •

edited

Loading

wgordon17 left a comment

arendej left a comment

xueli181114 May 10, 2022

EricPonvelle left a comment

xueli181114 commented May 11, 2022

Tessg22 left a comment

openshift-ci bot commented May 12, 2022

sayjadha commented May 12, 2022

wgordon17 left a comment

lpettyjo left a comment

lpettyjo Jun 17, 2022

sayjadha Jun 17, 2022

lpettyjo Jun 17, 2022

sayjadha Jun 17, 2022

lpettyjo Jun 17, 2022

sayjadha Jun 21, 2022

maxwelldb commented Jun 21, 2022

maxwelldb commented Jun 21, 2022

openshift-cherrypick-robot commented Jun 21, 2022

openshift-cherrypick-robot commented Jun 21, 2022


		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_policy/osd-life-cycle.adoc#osd-life-cycle[{product-title} update life cycle].
		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].

JIRA-OSDOCS3322: Updated the steps for cluster upgrades per the UI changes #44907

JIRA-OSDOCS3322: Updated the steps for cluster upgrades per the UI changes #44907

Conversation

sayjadha commented Apr 23, 2022 • edited Loading

netlify bot commented Apr 23, 2022 • edited Loading

✅ Deploy Preview for osdocs ready!

wgordon17 left a comment

Choose a reason for hiding this comment

arendej left a comment

Choose a reason for hiding this comment

xueli181114 May 10, 2022

Choose a reason for hiding this comment

EricPonvelle left a comment

Choose a reason for hiding this comment

xueli181114 commented May 11, 2022

Tessg22 left a comment

Choose a reason for hiding this comment

openshift-ci bot commented May 12, 2022

sayjadha commented May 12, 2022

wgordon17 left a comment

Choose a reason for hiding this comment

lpettyjo left a comment

Choose a reason for hiding this comment

lpettyjo Jun 17, 2022

Choose a reason for hiding this comment

sayjadha Jun 17, 2022

Choose a reason for hiding this comment

lpettyjo Jun 17, 2022

Choose a reason for hiding this comment

sayjadha Jun 17, 2022

Choose a reason for hiding this comment

lpettyjo Jun 17, 2022

Choose a reason for hiding this comment

sayjadha Jun 21, 2022

Choose a reason for hiding this comment

maxwelldb commented Jun 21, 2022

maxwelldb commented Jun 21, 2022

openshift-cherrypick-robot commented Jun 21, 2022

openshift-cherrypick-robot commented Jun 21, 2022

sayjadha commented Apr 23, 2022 •

edited

Loading

netlify bot commented Apr 23, 2022 •

edited

Loading