<commit_before>// Module included in the following assemblies:
//
// * updating/updating-cluster.adoc

[id="update-upgrading-web_{context}"]
= Updating a cluster by using the web console

If updates are available, you can update your cluster from the web console.

You can find information about available {product-title} advisories and updates
link:https://access.redhat.com/downloads/content/290/ver=4.1/rhel---7/4.1.0/x86_64/product-errata[in the errata section]
of the Customer Portal.

.Prerequisites

* Have access to the web console as a user with `admin` privileges.

.Procedure

. From the web console, click *Administration* > *Cluster Settings* and review
the contents of the *Overview* tab.
.. For production clusters, ensure that the *CHANNEL* is set to `stable-4.1`.
+
[IMPORTANT]
====
For production clusters, you must subscribe to the `stable-4.1` channel.
====
.. If the *UPDATE STATUS* is not *Updates Available*, you cannot upgrade your
cluster.
.. The *DESIRED VERSION* indicates the cluster version that your cluster is running
or is updating to.

. Click *Updates Available*, select a version to update to, and click *Update*.
The *UPDATE STATUS* changes to `Updating`, and you can review the progress of
the Operator upgrades on the *Cluster Operators* tab.<commit_msg>Bump version number in Updating a cluster topic<commit_after>// Module included in the following assemblies:
//
// * updating/updating-cluster.adoc

[id="update-upgrading-web_{context}"]
= Updating a cluster by using the web console

If updates are available, you can update your cluster from the web console.

You can find information about available {product-title} advisories and updates
link:https://access.redhat.com/downloads/content/290/ver=4.1/rhel---7/4.1.0/x86_64/product-errata[in the errata section]
of the Customer Portal.

.Prerequisites

* Have access to the web console as a user with `admin` privileges.

.Procedure

. From the web console, click *Administration* > *Cluster Settings* and review
the contents of the *Overview* tab.
.. For production clusters, ensure that the *CHANNEL* is set to `stable-4.2`.
+
[IMPORTANT]
====
For production clusters, you must subscribe to the `stable-4.2` channel.
====
.. If the *UPDATE STATUS* is not *Updates Available*, you cannot upgrade your
cluster.
.. The *DESIRED VERSION* indicates the cluster version that your cluster is running
or is updating to.

. Click *Updates Available*, select a version to update to, and click *Update*.
The *UPDATE STATUS* changes to `Updating`, and you can review the progress of
the Operator upgrades on the *Cluster Operators* tab.
{'fraction_non_alphanumeric': 0.0962566844919786, 'fraction_numerical': 0.012987012987012988, 'mean_word_length': 4.411157024793388, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3202323', 'n_tokens_mistral': 759, 'n_tokens_neox': 732, 'n_words': 332}