-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS-2477: Adds prerequisite step to updating cluster #36225
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
Conversation
|
✔️ Deploy Preview for osdocs ready! 🔨 Explore the source changes: f37bfb1 🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/6157182e7b06a8000790ee14 😎 Browse the preview: https://deploy-preview-36225--osdocs.netlify.app/openshift-enterprise/latest/updating/updating-cluster |
updating/updating-cluster-cli.adoc
Outdated
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.
I think we need some guidance around how an admin can check this.
cc @sdodson
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.
Reading through OSDOCS-2477 and the epic it's linked to I would interpret this to just mean that the admin addresses any of the conditions triggered by Upgradeable=False displayed either by the Console or oc adm upgrade cli command. I'm sure how to best address that in docs, perhaps something like the following
You must address any outstanding Upgradeable=False conditions before the cluster will allow an upgrade to the next minor. The output of oc adm upgrade will list all Upgradeable=False conditions and reasons for those conditions which will help you prepare for a minor version upgrade.
f009104 to
5d6679b
Compare
5d6679b to
e88a72b
Compare
2e5bf81 to
c73a0cd
Compare
e8a108b to
c1e5d03
Compare
updating/updating-cluster.adoc
Outdated
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 looks fine to me, but the admin console also displays these. As written this will work too but I don't know if we want to split the context between the cli upgrade and the admin console 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.
openshift/console#9329 illustrates how the admin console shows these in case you don't have a 4.9 cluster in front of you to look at
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.
@rhamilto Where is this displayed? Is it the banner that is at the top of the page?
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.
@opayne1 It's an alert at the top of the Administration -> Cluster Settings page.
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.
@spadgett @sdodson I watched the sprint demo of this as well. Am I making sense of this correctly?
| * Ensure you address all Upgradeable=False conditions so the cluster will allow an upgrade to the next minor version. You can run the command `oc adm upgrade` for an output of all Upgradeable=False conditions and the condition reasoning to help you prepare for a minor version upgrade. | |
| Ensure you address all Upgradeable=False conditions so the cluster will allow an upgrade to the next minor version. An alert will display at the top of the *Cluster Settings* page when you have one or more ClusterOperators that can not be upgraded. You will still be able to upgrade to the next available patch update for the minor release you are currently on. |
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.
@opayne1 yeah that sounds good to me.
c1e5d03 to
f97c1e3
Compare
f97c1e3 to
b1e23fe
Compare
b1e23fe to
ad41e60
Compare
ad41e60 to
d92eb5d
Compare
|
@yapei Please provide QE review for this. Thank you! |
|
the changes look good to me ~ ack |
bergerhoffer
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.
Just a few minor nits!
updating/updating-cluster-cli.adoc
Outdated
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.
- Ensure -> Ensure that
- Suggest putting
Upgradeable=Falsein backticks (2 places in this bullet) - cluster will allow -> cluster allows (to avoid future tense)
- I'd put "command" after
oc adm upgrade
updating/updating-cluster.adoc
Outdated
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.
Same comments from the above file (where applicable), plus:
- An alert will display -> An alert displays
- ClusterOperators -> cluster Operators
- can not -> cannot
- Reword "You will still be able to" to get rid of the future tense. Maybe "You can still"?
9e63637 to
f92694a
Compare
updating/updating-cluster-cli.adoc
Outdated
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.
backticks around second Upgradeable-False
updating/updating-cluster.adoc
Outdated
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.
s/ will allow/ allows
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.
cannot
|
lgtm! |
|
/cherrypick enterprise-4.9 |
|
@bobfuru: new pull request created: #36973 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/test-infra repository. |
OSDOCS-2477
enterprise-4.9+