Merge pull request #22252 from wking/recommend-no-channel

modules/understanding-upgrade-channels: Recommend clearing channel

Author: jeana-redhat

modules/understanding-upgrade-channels.adoc

@@ -21,6 +21,8 @@ ifndef::openshift-origin[]
 * `stable-{product-version}`
 * `eus-4.6` (only available when running 4.6)
 
+If you do not want the Cluster Version Operator to fetch available updates from the upgrade recommendation service, you can use the `oc adm upgrade channel` command in the OpenShift CLI to configure an empty channel. This configuration can be helpful if, for example, a cluster has restricted network access and there is no local, reachable upgrade recommendation service.
+
 endif::openshift-origin[]
 ifdef::openshift-origin[]
 {product-title} {product-version} offers the following upgrade channel:

updating/updating-cluster-between-minor.adoc

@@ -9,7 +9,7 @@ You can update, or upgrade, an {product-title} cluster between minor versions.
 
 [NOTE]
 ====
-Because of the difficulty of changing update channels by using `oc`, use the web console to change the update channel. It is recommended to complete the update process within the web console. You can follow the steps in xref:../updating/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster within a minor version by using the CLI] to complete the update after you change to a {product-version} channel.
+Use the web console or `oc adm upgrade channel _<channel>_` to change the update channel. You can follow the steps in xref:../updating/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster within a minor version by using the CLI] to complete the update after you change to a {product-version} channel.
 ====
 
 == Prerequisites