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).

OADP docs

We need to check how the OADP operator is installed after OCP 4.20