Merge pull request #14219 from kalexand-rh/ui_update

4.0 UI updates

Author: kalexand-rh

_topic_map.yml

@@ -70,6 +70,13 @@ Topics:
   - Name: Uninstalling a cluster on AWS
     File: uninstalling-cluster-aws
 ---
+Name: Updating clusters
+Dir: updating
+Distros: openshift-origin, openshift-enterprise
+Topics:
+- Name: Updating a cluster
+  File: updating-cluster
+---
 Name: Applications
 Dir: applications
 Distros: openshift-*

modules/update-service-overview.adoc

@@ -1,28 +1,35 @@
 // Module included in the following assemblies:
 //
 // * architecture/architecture.adoc
+// * upgrading/upgrading-cluster.adoc
 
 [id="update-service-overview-{context}"]
-== The {product-title} update service
+= About the {product-title} update service
 
-The {product-title} update service is the hosted service that provides over the air updates to both
-{product-title} and {op-system-first}. It provides a graph, or diagram that contain
-_vertices_ and the _edges_ that connect them, of component Operators. The edges
-in the graph show which versions you can safely upgrade to, and the vertices
-are update payloads that specify the intended state of the managed cluster components.
-The Cluster Version Operator checks with the {product-title} update service and determines valid upgrades and upgrade paths
-based on current component versions and information in the graph. If you
-configure it to do so, the {product-title} update service sends the release artifacts that it needs to
-perform the upgrade to your image registry, and the Cluster Version Operator
-upgrades your cluster. By accepting automatic updates, you can automatically
+The {product-title} update service is the hosted service that provides over-the-air
+updates to both {product-title} and {op-system-first}. It provides a graph,
+or diagram that contain _vertices_ and the _edges_ that connect them, of
+component Operators. The edges in the graph show which versions you can safely
+update to, and the vertices are update payloads that specify the intended state
+of the managed cluster components.
+
+The Cluster Version Operator (CVO) in your cluster checks with the
+{product-title} update service to see the valid updates and update paths based
+on current component versions and information in the graph. When you request an
+update, the {product-title} CVO uses the release image for that update to
+upgrade your cluster. The release artifacts are hosted in Quay as container
+images.
+////
+By accepting automatic updates, you can automatically
 keep your cluster up to date with the most recent compatible components.
+////
 
-To allow the {product-title} update service to provide only compatible updates, a release verification
-pipeline exists to drive automation. Each release artifact is verified for
-compatibility with supported cloud platforms and system architectures as well
-as other component packages. After the pipeline confirms the suitability of a
-release, the {product-title} update service can apply the update to your cluster or notify you that it
-is available.
+To allow the {product-title} update service to provide only compatible updates,
+a release verification pipeline exists to drive automation. Each release
+artifact is verified for compatibility with supported cloud platforms and system
+architectures as well as other component packages. After the pipeline confirms
+the suitability of a release, the {product-title} update service can apply the
+update to your cluster or notify you that it is available.
 
 ////
 The interaction between the registry and the {product-title} update service is different during
@@ -38,4 +45,4 @@ During continuous update mode, two controllers run. One continuously updates
 the payload manifests, applies them to the cluster, and outputs the status of
 the controlled rollout of the Operators, whether they are available, upgrading,
 or failed. The second controller polls the {product-title} update service to
-determine if updates are available.
+determine if updates are available.

modules/upgrade-upgrading-web.adoc

@@ -0,0 +1,26 @@
+// Module included in the following assemblies:
+//
+// * upgrading/upgrading-cluster.adoc
+
+[id='upgrade-upgrading-web-{context}']
+= Updating a cluster by using the web console
+
+If updates are available, you can update your cluster from the web console.
+
+.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.0`.
+.. 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.

upgrading/images renamed to updating/images

@@ -0,0 +1,17 @@
+[id='updating-cluster']
+= Updating a cluster
+include::modules/common-attributes.adoc[]
+:context: updating-cluster
+
+toc::[]
+
+You can update, or upgrade, an {product-title} cluster.
+
+.Prerequisites
+
+* Access to the cluster as a user with `admin` privileges.
+See xref:../authentication/using-rbac.adoc[Using RBAC to define and apply permissions].
+
+include::modules/update-service-overview.adoc[leveloffset=+1]
+
+include::modules/upgrade-upgrading-web.adoc[leveloffset=+1]