This guide walks cluster administrators through installing Operators to an OpenShift Dedicated cluster.
As a cluster administrator, you can install an Operator from the OperatorHub
using the OpenShift Dedicated
web console. You can then subscribe the Operator to the default
openshift-operators namespace to make it available for developers on your
In OpenShift Dedicated clusters, a curated list of Operators is made available for
installation from the OperatorHub. Administrators can only install Operators to
openshift-operators namespace, except for the Logging Operator,
which requires the
Privileged and custom Operators cannot be installed.
During installation, you must determine the following initial settings for the Operator:
In OpenShift Dedicated clusters, you can choose All namespaces on the cluster (default) to have the Operator installed on all namespaces. This makes the Operator available to all users and projects.
If an Operator is available through multiple channels, you can choose which channel you want to subscribe to. For example, to deploy from the stable channel, if available, select it from the list.
You can choose Automatic or Manual updates. If you choose Automatic updates for an installed Operator, when a new version of that Operator is available, the Operator Lifecycle Manager (OLM) automatically upgrades the running instance of your Operator without human intervention. If you select Manual updates, when a newer version of an Operator is available, the OLM creates an update request. As a cluster administrator, you must then manually approve that update request to have the Operator updated to the new version.
This procedure uses the Couchbase Operator as an example to install and subscribe to an Operator from the OperatorHub using the OpenShift Dedicated web console.
Access to an OpenShift Dedicated cluster using an account with
Navigate in the web console to the Operators → OperatorHub page.
Scroll or type a keyword into the Filter by keyword box (in this case,
Couchbase) to find the Operator you want.
Select the Operator. For a Community Operator, you are warned that Red Hat does not certify those Operators. You must acknowledge that warning before continuing. Information about the Operator is displayed.
Read the information about the Operator and click Install.
On the Create Operator Subscription page:
Select one of the following:
All namespaces on the cluster (default) installs the Operator in the default
openshift-operators namespace to watch and be made available to all namespaces
in the cluster. This option is not always available.
A specific namespace on the cluster allows you to choose a specific, single
namespace in which to install the Operator. The Operator will only watch and be
made available for use in this single namespace.
If you are installing the Cluster Logging Operator, choose this option to select
Select an Update Channel (if more than one is available).
Select Automatic or Manual approval strategy, as described earlier.
Click Subscribe to make the Operator available to the selected namespaces on this OpenShift Dedicated cluster.
If you selected a Manual approval strategy, the Subscription’s upgrade status will remain Upgrading until you review and approve its Install Plan.
After approving on the Install Plan page, the Subscription upgrade status moves to Up to date.
If you selected an Automatic approval strategy, the upgrade status should resolve to Up to date without intervention.
After the Subscription’s upgrade status is Up to date, select Operators → Installed Operators to verify that the Couchbase ClusterServiceVersion (CSV) eventually shows up and its Status ultimately resolves to InstallSucceeded in the relevant namespace.
For the All namespaces… Installation Mode, the status resolves to
InstallSucceeded in the
If it does not:
Check the logs in any Pods in the
openshift-operators project (or other
relevant namespace if A specific namespace… Installation Mode was selected)
on the Workloads → Pods page that are reporting issues to troubleshoot