Skip to content

Commit abdb0bb

Browse files
committed
OBSDOCS-550-installation-docs-for-cluster-observability-operator
1 parent 4d54edf commit abdb0bb

File tree

4 files changed

+49
-1
lines changed

4 files changed

+49
-1
lines changed

_topic_maps/_topic_map.yml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2611,6 +2611,15 @@ Topics:
26112611
File: troubleshooting-monitoring-issues
26122612
- Name: Config map reference for the Cluster Monitoring Operator
26132613
File: config-map-reference-for-the-cluster-monitoring-operator
2614+
- Name: Cluster Observability Operator
2615+
Dir: cluster_observability_operator
2616+
Topics:
2617+
- Name: Cluster Observability Operator release notes
2618+
File: cluster-observability-operator-release-notes
2619+
- Name: Cluster Observability Operator overview
2620+
File: cluster-observability-operator-overview
2621+
- Name: Installing the Cluster Observability Operator
2622+
File: installing-the-cluster-observability-operator
26142623
---
26152624
Name: Network Observability
26162625
Dir: network_observability
Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
// Module included in the following assemblies:
2+
3+
// * monitoring/cluster_observability_operator/installing-the-cluster-observability-operator.adoc
4+
5+
:_mod-docs-content-type: PROCEDURE
6+
[id="uninstalling-the-cluster-observability-operator-using-the-web-console_{context}"]
7+
= Uninstalling the Cluster Observability Operator using the web console
8+
If you have installed the Cluster Observability Operator (COO) by using OperatorHub, you can uninstall it in the {product-title} web console.
9+
10+
.Prerequisites
11+
12+
* You have access to the cluster as a user with the `cluster-admin` cluster role.
13+
* You have logged in to the {product-title} web console.
14+
15+
.Procedure
16+
17+
. Go to *Operators* -> *Installed Operators*.
18+
19+
. Locate the *Cluster Observability Operator* entry in the list.
20+
21+
. Click {kebab} for this entry and select *Uninstall Operator*.

monitoring/cluster_observability_operator/cluster-observability-operator-overview.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
:FeatureName: Using the Cluster Observability Operator
9+
:FeatureName: The Cluster Observability Operator
1010
include::snippets/technology-preview.adoc[leveloffset=+2]
1111

1212
The Cluster Observability Operator (COO) is an optional component of the {product-title}. You can deploy it to create standalone monitoring stacks that are independently configurable for use by different services and users.
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="installing-cluster-observability-operators"]
3+
= Installing the Cluster Observability Operator
4+
include::_attributes/common-attributes.adoc[]
5+
:context: installing_the_cluster_observability_operator
6+
7+
toc::[]
8+
9+
:FeatureName: The Cluster Observability Operator
10+
include::snippets/technology-preview.adoc[leveloffset=+2]
11+
12+
As a cluster administrator, you can install the Cluster Observability Operator (COO) from OperatorHub by using the {product-title} web console or CLI.
13+
OperatorHub is a user interface that works in conjunction with Operator Lifecycle Manager (OLM), which installs and manages Operators on a cluster.
14+
15+
To install the COO using OperatorHub, follow the procedure described in xref:../../operators/admin/olm-adding-operators-to-cluster.adoc[Adding Operators to a cluster].
16+
17+
// Uninstalling COO using the OCP web console
18+
include::modules/monitoring-uninstalling-cluster-observability-operator-using-the-web-console.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)