[OCPBUGS#9167]: Updated oc adm upgrade output to reflect 4.14 oc client #65618
[OCPBUGS#9167]: Updated oc adm upgrade output to reflect 4.14 oc client #65618skrthomas merged 1 commit intoopenshift:mainfrom
Conversation
|
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/27179 |
0b11f13 to
51d9c66
Compare
| ==== | ||
|
|
||
| . Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.12`, `fast-4.12`, or `eus-4.12`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section. | ||
| . Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13`, `fast-4.13`, or `eus-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section. |
There was a problem hiding this comment.
There's no eus-4.13, it's only for even releases. So 4.13.z releases will only show up in an eus-4.14 channel, and even that won't happen until 45 to 90 days after 4.14 GAs.
|
|
||
| Upstream is unset, so the cluster will use an appropriate default. | ||
| Channel: stable-4.10 (available channels: candidate-4.10, candidate-4.11, eus-4.10, fast-4.10, fast-4.11, stable-4.10) | ||
| Channel: stable-version (available channels: candidate-version, eus-version, fast-version, stable-version) |
There was a problem hiding this comment.
Down below, you're using <version>. I'm agnostic about whether you want to mark these placeholders or not, but whichever way you go, it's probably worth being consistent.
| ==== | ||
|
|
||
| . Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.12`, `fast-4.12`, or `eus-4.12`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section. | ||
| . Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section. |
There was a problem hiding this comment.
we can keep the reference to fast-4.13 here. It's everything from Channel: ... (available channels: <anything from here>), with the caveat that candidate-4.y channels will not limit you to supported releases.
|
|
||
| Upstream is unset, so the cluster will use an appropriate default. | ||
| Channel: stable-4.10 (available channels: candidate-4.10, candidate-4.11, eus-4.10, fast-4.10, fast-4.11, stable-4.10) | ||
| Channel: stable-<version> (available channels: candidate-<version>, eus-<version>, fast-<version>, <stable-version>) |
There was a problem hiding this comment.
nit: <stable-version> -> stable-<version>.
|
|
||
| Upstream is unset, so the cluster will use an appropriate default. | ||
| Channel: stable-4.10 (available channels: candidate-4.10, candidate-4.11, eus-4.10, fast-4.10, fast-4.11, stable-4.10) | ||
| Channel: stable-<version> (available channels: candidate-<version>, eus-<version>, fast-<version>, stable-<version>) |
There was a problem hiding this comment.
It's the output of oc adm upgrade instead of oc get clusterversion in line https://github.com/openshift/openshift-docs/pull/65618/files#diff-a4543a07ef809868d1b552e88f1c5a5b4dbbc99a3ff5c769ec4ad63cd55d0b4dL120
We can update it to oc adm upgrade
58466be to
bd8b168
Compare
bd8b168 to
2c88d0c
Compare
|
/label peer-review-needed |
bburt-rh
left a comment
There was a problem hiding this comment.
One tiny nitpick, but otherwise lgtm! Thank you.
| ==== | ||
|
|
||
| . Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.12`, `fast-4.12`, or `eus-4.12`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section. | ||
| . Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13` or `fast-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section. |
There was a problem hiding this comment.
| . Based on your organization requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13` or `fast-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the Additional resources section. | |
| . Based on your organization's requirements, set the appropriate update channel. For example, you can set your channel to `stable-4.13` or `fast-4.13`. For more information about channels, refer to _Understanding update channels and releases_ listed in the "Additional resources" section. |
- Per ISG, "If you refer to a smaller piece of work within a larger container such as a chapter within a book or an article in a magazine, use italic font for the larger container and double quotation marks for the smaller piece."
2c88d0c to
4d90d6d
Compare
4d90d6d to
c041f25
Compare
|
/label merge-review-needed |
|
/cherrypick enterprise-4.14 |
|
@skrthomas: new pull request created: #65964 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. |
Version(s):
4.14+
Issue:
https://issues.redhat.com/browse/OCPBUGS-9167
Link to docs preview:
https://65618--docspreview.netlify.app/openshift-enterprise/latest/updating/updating_a_cluster/updating-cluster-cli#update-upgrading-cli_updating-cluster-cli
QE review: