-
Notifications
You must be signed in to change notification settings - Fork 1.9k
ROX-14221: upgrade procedures for cloud #78259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ROX-14221: upgrade procedures for cloud #78259
Conversation
|
@kcarmichael08: This pull request references ROX-14221 which is a valid jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Tue Jul 16 21:48:55 - Prow CI generated the docs preview: |
|
@kcarmichael08: This pull request references ROX-14221 which is a valid jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
0bc3a7b to
1e450db
Compare
|
/retest |
2c271a1 to
336a2c6
Compare
|
@kcarmichael08: This pull request references ROX-14221 which is a valid jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
f39aeae to
e643462
Compare
|
/retest |
e643462 to
b9d567a
Compare
|
/retest deploy-preview |
f8aa662 to
86deb12
Compare
|
@kcarmichael08: This pull request references ROX-14221 which is a valid jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
86deb12 to
e532cdd
Compare
|
@kcarmichael08: This pull request references ROX-14221 which is a valid jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
lahinson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job on this large doc set! I made a few suggestions based on IBM Style and the OCP doc guidelines.
| [role="_abstract"] | ||
| You can upgrade your secured clusters in {product-title-managed-short} by using Helm charts. | ||
|
|
||
| If you have installed {product-title-short} secured clusters by using Helm charts, to upgrade to the latest version of {product-title-short} perform the following steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| If you have installed {product-title-short} secured clusters by using Helm charts, to upgrade to the latest version of {product-title-short} perform the following steps: | |
| If you installed {product-title-short} secured clusters by using Helm charts, you can upgrade to the latest version of {product-title-short} by updating the Helm chart and running the `helm upgrade` command. |
- I removed the ordered list because in the preview, it looked like there was a procedure in the assembly, when the procedure is actually further down the page.
- Removed "have" to use the simple present tense, per IBM Style.
- IBM Style word usage advises against the term "perform" in technical content.
|
|
||
| If you have installed {product-title-short} secured clusters by using Helm charts, to upgrade to the latest version of {product-title-short} perform the following steps: | ||
|
|
||
| . Update the Helm chart. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| . Update the Helm chart. |
| If you have installed {product-title-short} secured clusters by using Helm charts, to upgrade to the latest version of {product-title-short} perform the following steps: | ||
|
|
||
| . Update the Helm chart. | ||
| . Run the `helm upgrade` command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| . Run the `helm upgrade` command. |
| . Update the Helm chart. | ||
| . Run the `helm upgrade` command. | ||
|
|
||
| [role="_additional-resources"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| [role="_additional-resources"] |
In the preview, it looks like maybe the "Updating the Helm chart repository" module is mixed up with an "Additional resources" section.
| . Run the `helm upgrade` command. | ||
|
|
||
| [role="_additional-resources"] | ||
| .Additional resources |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| .Additional resources |
| ---- | ||
|
|
||
| endif::cloud-svc[] | ||
| . To add the required roles and role bindings to use the {osp} SCCs for all secured clusters, perform the following steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| . To add the required roles and role bindings to use the {osp} SCCs for all secured clusters, perform the following steps: | |
| . To add the required roles and role bindings to use the {osp} SCCs for all secured clusters, complete the following steps: |
| ==== | ||
| You must change the subscription channel for all clusters where you have installed {product-title-short} Operator, including Central and all Secured clusters. | ||
| ifndef::cloud-svc[] | ||
| You must change the subscription channel for all clusters where you have installed the {product-title-short} Operator, including Central and all Secured clusters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| You must change the subscription channel for all clusters where you have installed the {product-title-short} Operator, including Central and all Secured clusters. | |
| You must change the subscription channel for all clusters where you installed the {product-title-short} Operator, including Central and all Secured clusters. |
| You must change the subscription channel for all clusters where you have installed the {product-title-short} Operator, including Central and all Secured clusters. | ||
| endif::[] | ||
| ifdef::cloud-svc[] | ||
| You must change the subscription channel for all secured clusters where you have installed the {product-title-short} Operator. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| You must change the subscription channel for all secured clusters where you have installed the {product-title-short} Operator. | |
| You must change the subscription channel for all secured clusters where you installed the {product-title-short} Operator. |
| .Prerequisites | ||
| ifndef::cloud-svc[] | ||
| * You must verify that you are using the latest {product-title-short} 3.74 Operator and there are no pending manual Operator upgrades. | ||
| * You must verify that you have backed up your existing Central database. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * You must verify that you have backed up your existing Central database. | |
| * You must verify that you backed up your Central database. |
| <1> If you use Kubernetes, enter `kubectl` instead of `oc`. | ||
|
|
||
| During the update the {product-title-short} Operator provisions a new deployment called `central-db` and your data begins migrating. It takes around 30 minutes and only happens once when you upgrade. | ||
| During the update the {product-title-short} Operator provisions a new deployment called `central-db` and your data begins migrating. It takes around 30 minutes and only happens after when you upgrade. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| During the update the {product-title-short} Operator provisions a new deployment called `central-db` and your data begins migrating. It takes around 30 minutes and only happens after when you upgrade. | |
| During the update, the {product-title-short} Operator provisions a new deployment called `central-db` and your data begins migrating. It takes around 30 minutes and only happens after when you upgrade. |
In the second sentence, I'm not sure what you mean by "...and only happens after when you upgrade."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is existing text, so I will ask (I don't know the answer).
e532cdd to
6e07f71
Compare
|
/retest |
1 similar comment
|
/retest |
6e07f71 to
04e22ea
Compare
04e22ea to
8c03b55
Compare
|
@kcarmichael08: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
|
/cherrypick rhacs-docs-4.4 |
|
/cherrypick rhacs-docs-4.5 |
|
@kcarmichael08: #78259 failed to apply on top of branch "rhacs-docs-4.4": DetailsIn response to this:
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-sigs/prow repository. |
|
@kcarmichael08: new pull request created: #78968 DetailsIn response to this:
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-sigs/prow repository. |
Version(s):
4.4+
Issue
Links to docs previews:
https://78259--ocpdocs-pr.netlify.app/openshift-acs/latest/cloud_service/upgrading-cloud/upgrade-cloudsvc-operator
https://78259--ocpdocs-pr.netlify.app/openshift-acs/latest/cloud_service/upgrading-cloud/upgrade-cloudsvc-helm
https://78259--ocpdocs-pr.netlify.app/openshift-acs/latest/cloud_service/upgrading-cloud/upgrade-cloudsvc-roxctl
QE review:
Additional information:
Note to technical reviewers:
This material is reused from the RHACS docs where applicable. I have removed references to Central, but if there are things in these docs that do not apply to Cloud, please mark in your review. Thank you!