In OCP 4.20, the console is introducing the combined software catalog. This is an incremental step in introducing console support for OLM v1 (planned for TP in 4.21 and GA in 4.22). This is also a means to integrate Helm charts with the RH and custom catalogs in a single heading.

As a result, instead of Operators > OperatorHub to install an Operator, customers need to go to Ecosystem > Software catalog. If the customer is not already in a specific namespace/project, they need to select or create one before seeing the catalog.

This means that the first few steps of every layered product and RH Operator need to eventually be updated. (discussions between CS and DPM are ongoing).

As a starting point, this ticket tracks the work to update the OLM v0 docs for installing an Operator from the UI.

This could be used as a reference for other writers to update their docs.

ATM, we are unsure if there are broader impacts on the Operator install, update, delete, and lifecycling experience.

MTV docs

Check how the MTV operator is installed