ROX-24162: Upgrade instructions for 4.5+ #77179
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@kcarmichael08: This pull request references ROX-24162 which is a valid jira issue. In 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. |
openshift-ci
bot
added
the
size/XS
|
🤖 Tue Jun 11 19:44:34 - Prow CI generated the docs preview: https://77179--ocpdocs-pr.netlify.app/openshift-acs/latest/upgrading/upgrade-helm.html |
|
@kcarmichael08: This pull request references ROX-24162 which is a valid jira issue. In 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. |
|
@kcarmichael08: This pull request references ROX-24162 which is a valid jira issue. In 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. |
msugakov
left a comment
msugakov
left a comment
There was a problem hiding this comment.
Thanks for taking care of this Kerry!
The operator is covered by that part
When upgrading Operator-based Central deployments from version 3.74, first ensure the Operator upgrade mode is set to Manual. Then, upgrade the Operator to version 4.0 following the procedure in the upgrade documentation for version 4.0 and ensure that Central is online. After the upgrade to version 4.0 is complete, Red Hat recommends upgrading Central to the latest version for full functionality.
and so we don't need to write anything extra.
kcarmichael08
added
rhacs-docs-4.5
peer-review-needed
mletalie
left a comment
mletalie
left a comment
There was a problem hiding this comment.
/label peer-review-in-progress
openshift-ci
bot
added
the
peer-review-in-progress
|
Hello @kcarmichael08, |
mletalie
left a comment
mletalie
left a comment
There was a problem hiding this comment.
/label peer-review-done
/remove-label peer-review-needed
/remove-label peer-review-in-progress
/lgtm
|
|
||
| When upgrading from earlier releases, follow this guidance: | ||
|
|
||
| * If the release for Central is earlier than 3.74, you must upgrade to the latest 3.74 patch before upgrading to a 4.x release. See the link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_security_for_kubernetes/3.74/html/upgrading/index[upgrade documentation for version 3.74] for information about upgrades from earlier versions to 3.74. |
There was a problem hiding this comment.
| * If the release for Central is earlier than 3.74, you must upgrade to the latest 3.74 patch before upgrading to a 4.x release. See the link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_security_for_kubernetes/3.74/html/upgrading/index[upgrade documentation for version 3.74] for information about upgrades from earlier versions to 3.74. | |
| * If the release for Central is earlier than 3.74, you must upgrade to the latest 3.74 patch before upgrading to a 4.x release. See the link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_security_for_kubernetes/3.74/html/upgrading/index[upgrade documentation for version 3.74] for information about upgrades from earlier versions through 3.74. |
There was a problem hiding this comment.
After thinking about it, I think "to" is better than "through" since the documentation being referred to describes upgrading to 3.74 and not any other versions before 3.74.... Basically, everyone needs to upgrade to a minimum of 3.74 before then upgrading to 4.0+ (there is no 3.75). I hope that makes sense.
There was a problem hiding this comment.
Thanks, I do appreciate the suggestions and the peer review though!
openshift-ci
bot
added
peer-review-done
|
@kcarmichael08: This pull request references ROX-24162 which is a valid jira issue. In 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. |
kcarmichael08
force-pushed
the
ROX-24162-upgrade-4.5
branch
from
c3ce30d to
3aec0a6
Compare
|
New changes are detected. LGTM label has been removed. |
|
@kcarmichael08: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
/cherrypick rhacs-docs-4.5 |
|
@kcarmichael08: new pull request created: #77333 In 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. |
6 participants
Version(s):
RHACS 4.5+
Issue
Link to docs preview
QE review:
Additional information:
See also #65388
Do we need changes to the Operator section? (I don't think so, but wanted to check.) https://77179--ocpdocs-pr.netlify.app/openshift-acs/latest/upgrading/upgrade-operator