Merge pull request #74919 from bburt-rh/OBSDOCS-613-expanded-install-docs-for-COO

OBSDOCS-613: expanded-install-docs-for-COO

Author: bburt-rh

modules/monitoring-installing-cluster-observability-operator-using-the-web-console.adoc

@@ -0,0 +1,34 @@
+// Module included in the following assemblies:
+
+// * observability/monitoring/cluster_observability_operator/installing-the-cluster-observability-operator.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="installing-the-cluster-observability-operator-in-the-web-console-_{context}"]
+= Installing the {coo-full} in the web console
+Install the {coo-first} from OperatorHub by using the {product-title} web console.
+
+.Prerequisites
+
+* You have access to the cluster as a user with the `cluster-admin` cluster role.
+* You have logged in to the {product-title} web console.
+
+.Procedure
+
+. In the {product-title} web console, click *Operators* -> *OperatorHub*.
+. Type `cluster observability operator` in the *Filter by keyword* box.
+. Click  *{coo-full}* in the list of results.
+. Read the information about the Operator, and review the following default installation settings:
++
+* *Update channel* -> *development*
+* *Version* -> <most_recent_version>
+* *Installation mode* -> *All namespaces on the cluster (default)*
+* *Installed Namespace* -> *openshift-operators*
+* *Update approval* -> *Automatic*
+
+. Optional: Change default installation settings to suit your requirements.
+For example, you can select to subscribe to a different update channel, to install an older released version of the Operator, or to require manual approval for updates to new versions of the Operator.
+. Click *Install*.
+
+.Verification
+
+* Go to *Operators* -> *Installed Operators*, and verify that the *{coo-full}* entry appears in the list.

modules/monitoring-uninstalling-cluster-observability-operator-using-the-web-console.adoc

@@ -19,3 +19,7 @@ If you have installed the {coo-first} by using OperatorHub, you can uninstall it
 . Locate the *{coo-full}* entry in the list.
 
 . Click {kebab} for this entry and select *Uninstall Operator*.
+
+.Verification
+
+* Go to *Operators* -> *Installed Operators*, and verify that the *{coo-full}* entry no longer appears in the list.

observability/monitoring/cluster_observability_operator/installing-the-cluster-observability-operator.adoc

@@ -9,10 +9,14 @@ toc::[]
 :FeatureName: The Cluster Observability Operator
 include::snippets/technology-preview.adoc[leveloffset=+2]
 
-As a cluster administrator, you can install the {coo-first} from OperatorHub by using the {product-title} web console or CLI.
+As a cluster administrator, you can install or remove the {coo-first} from OperatorHub by using the {product-title} web console.
 OperatorHub is a user interface that works in conjunction with Operator Lifecycle Manager (OLM), which installs and manages Operators on a cluster.
 
-To install the {coo-short} using OperatorHub, follow the procedure described in xref:../../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-adding-operators-to-a-cluster[Adding Operators to a cluster].
+// Installing the COO using the OCP web console
+include::modules/monitoring-installing-cluster-observability-operator-using-the-web-console.adoc[leveloffset=+1]
+
+.Additional resources
+xref:../../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-adding-operators-to-a-cluster[Adding Operators to a cluster]
 
 // Uninstalling COO using the OCP web console
 include::modules/monitoring-uninstalling-cluster-observability-operator-using-the-web-console.adoc[leveloffset=+1]