[enterprise-4.9]OSDOCS-3605-and-Gh-issue-40595: Updates cluster CLI update procedure

[darshan-nagaraj]

Version(s): 4.9

Issue: https://issues.redhat.com/browse/OSDOCS-3605 and #40595

Link to docs preview: http://file.rdu.redhat.com/dnagaraj/OSDOCS-3605-and-Gh-issue-40595/updating/updating-cluster-cli.html#update-upgrading-cli_updating-cluster-cli

Additional information: Relates to #45326 and #45663

[tmalove]

LGTM

[wking]

openshift/oc#576 landed in the development branch and shipped with 4.9. So folks using a 4.8 oc won't have the channel subcommand available. That is narrowly acceptable, because we open this file with:

Install the OpenShift CLI (oc) that matches the version for your updated version.

But I'm not sure how many folks are following along that carefully, so it might be worth a reminder here that we want them to be using a 4.9 oc for this pre-update channel change, even though they are currently running a 4.8 cluster.

[wking]

/lgtm

I'm fine with or without this adjustment.

[jeana-redhat]

Minor nits, mostly just the standard around "by running the following command" for commands.

[jeana-redhat]

Suggested change

	. View the available updates and note the version number of the update that
	you want to apply:
	. View the available updates by running the following command. Note the version number of the update that you want to apply.

[jeana-redhat]

Suggested change

	. Based on your organization requirements, set the upgrade channel to `stable-4.9`, `fast-4.9`, or `eus-4.10`:
	. Based on your organization requirements, set the upgrade channel to `stable-4.9`, `fast-4.9`, or `eus-4.10` by running the following command:

[jeana-redhat]

Suggested change

	For example, to set the channel to `stable-4.9`:
	For example, to set the channel to `stable-4.9`, run the following command:

[jiajliu]

The step 2 and step 3 should be switched. We should set channel correctly first, and then it will show available update correctly. For example in this pr, if users don't set channel to stable-4.9 as step 3, then the available update should not be like the one in step 2(including v4.9.*)

[jiajliu]

A quick check on v4.10, the same issue.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.