This guide walks cluster administrators through the process of installing the Service Binding Operator to an OKD cluster.
You can install Service Binding Operator on OKD 4.7 and later.
You have access to an OKD cluster using an account with
Your cluster has the Marketplace capability enabled or the Red Hat Operator catalog source configured manually.
You can install Service Binding Operator using the OKD OperatorHub. When you install the Service Binding Operator, the custom resources (CRs) required for the service binding configuration are automatically installed along with the Operator.
In the Administrator perspective of the web console, navigate to Operators → OperatorHub.
Use the Filter by keyword box to search for
Service Binding Operator in the catalog. Click the Service Binding Operator tile.
Read the brief description about the Operator on the Service Binding Operator page. Click Install.
On the Install Operator page:
Select All namespaces on the cluster (default) for the Installation Mode. This mode installs the Operator in the default
openshift-operators namespace, which enables the Operator to watch and be made available to all namespaces in the cluster.
Select Automatic for the Approval Strategy. This ensures that the future upgrades to the Operator are handled automatically by the Operator Lifecycle Manager (OLM). If you select the Manual approval strategy, OLM creates an update request. As a cluster administrator, you must then manually approve the OLM update request to update the Operator to the new version.
Select an Update Channel.
By default, the stable channel enables installation of the latest stable and supported release of the Service Binding Operator.
The Operator is installed automatically into the
On the Installed Operator — ready for use pane, click View Operator. You will see the Operator listed on the Installed Operators page.
Verify that the Status is set to Succeeded to confirm successful installation of Service Binding Operator.