Skip to content

OBSDOCS-2799 OperatorHub to Software Catalog, Operators to Ecosystemfor 4.20 #102275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 14, 2025
Merged

OBSDOCS-2799 OperatorHub to Software Catalog, Operators to Ecosystemfor 4.20 #102275

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions installing/installing-the-cluster-observability-operator.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,12 @@ toc::[]
As a cluster administrator, you can install or remove the {coo-first} from OperatorHub by using the {ocp-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.

[NOTE]
====
For {ocp-product-title} v4.20+, you can install an Operator using the software catalog.
====


// Installing the COO using the OCP web console
include::modules/monitoring-installing-cluster-observability-operator-using-the-web-console.adoc[leveloffset=+1]

Expand Down
9 changes: 7 additions & 2 deletions ...monitoring-installing-cluster-observability-operator-using-the-web-console.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,9 @@ Install the {coo-first} from OperatorHub by using the {ocp-product-title} web co

.Procedure

. In the {ocp-product-title} web console, click *Operators* -> *OperatorHub*.
. In the {ocp-product-title} web console:
.. Click *Operators* -> *OperatorHub*, if your version of {ocp-product-title} is 4.19 or earlier.
.. Click *Ecosystem* -> *Software Catalog*, if your version of {ocp-product-title} is 4.20+.
. 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 configure the following installation settings:
Expand All @@ -32,4 +34,7 @@ For example, you can select to subscribe to a different update channel, to insta

.Verification

* Go to *Operators* -> *Installed Operators*, and verify that the *{coo-full}* entry appears in the list.
* In the {ocp-product-title} web console:
** Go to *Operators* -> *Installed Operators*, if your version of {ocp-product-title} is 4.19 or earlier.
** Go to *Ecosystem* -> *Installed Operators*, if your version of {ocp-product-title} is 4.20+.
* Verify that the *{coo-full}* entry appears in the list.
12 changes: 8 additions & 4 deletions ...nitoring-uninstalling-cluster-observability-operator-using-the-web-console.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
:_mod-docs-content-type: PROCEDURE
[id="uninstalling-the-cluster-observability-operator-using-the-web-console_{context}"]
= Uninstalling the {coo-full} using the web console
If you have installed the {coo-first} by using OperatorHub, you can uninstall it in the {ocp-product-title} web console.
If you have installed the {coo-first} by using OperatorHub or software catalog, you can uninstall it in the {ocp-product-title} web console.

.Prerequisites

Expand All @@ -14,12 +14,16 @@ If you have installed the {coo-first} by using OperatorHub, you can uninstall it

.Procedure

. Go to *Operators* -> *Installed Operators*.

. In the {ocp-product-title} web console:
.. Go to *Operators* -> *Installed Operators*, if your version of {ocp-product-title} is 4.19 or earlier.
.. Go to *Ecosystem* -> *Installed Operators*, if your version of {ocp-product-title} is 4.20+.
. 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.
* In the {ocp-product-title} web console:
** Go to *Operators* -> *Installed Operators*, if your version of {ocp-product-title} is 4.19 or earlier.
** Go to *Ecosystem* -> *Installed Operators*, if your version of {ocp-product-title} is 4.20+.
* Verify that the *{coo-full}* entry no longer appears in the list.