mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
40 lines
1.4 KiB
Plaintext
40 lines
1.4 KiB
Plaintext
// Module included in the following assemblies:
|
|
// * updating/updating_a_cluster/updating_disconnected_cluster/disconnected-update-osus.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="update-service-install-web-console_{context}"]
|
|
= Installing the OpenShift Update Service Operator by using the web console
|
|
|
|
You can use the web console to install the OpenShift Update Service Operator.
|
|
|
|
.Procedure
|
|
|
|
. In the web console, click *Ecosystem* -> *Software Catalog*.
|
|
+
|
|
[NOTE]
|
|
====
|
|
Enter `Update Service` into the *Filter by keyword...* field to find the Operator faster.
|
|
====
|
|
|
|
. Choose *OpenShift Update Service* from the list of available Operators, and click *Install*.
|
|
|
|
.. Select an *Update channel*.
|
|
|
|
.. Select a *Version*.
|
|
|
|
.. Select *A specific namespace on the cluster* under *Installation Mode*.
|
|
|
|
.. Select a namespace for *Installed Namespace* or accept the recommended namespace `openshift-update-service`.
|
|
|
|
.. Select an *Update approval* strategy:
|
|
+
|
|
** The *Automatic* strategy allows Operator Lifecycle Manager (OLM) to automatically update the Operator when a new version is available.
|
|
+
|
|
** The *Manual* strategy requires a cluster administrator to approve the Operator update.
|
|
|
|
.. Click *Install*.
|
|
|
|
. Go to *Ecosystem* -> *Installed Operators* and verify that the OpenShift Update Service Operator is installed.
|
|
|
|
. Ensure that *OpenShift Update Service* is listed in the correct namespace with a *Status* of *Succeeded*.
|