Installing Service Binding Operator
This document walks you through the steps to install Service Binding Operator v0.3.0 on OpenShift cluster and Service Binding Operator v0.4.0 on Kubernetes cluster.
Why do I need the Service Binding Operator?
odo uses Service Binding Operator to provide the odo link
feature which helps connect an odo component to a service or another component.
Installing Service Binding Operator on OpenShift
To install Service Binding Operator on OpenShift, refer this video.
Installing Service Binding Operator on Kubernetes
To install the Operator, execute the following kubectl
command provided on its OperatorHub.io page:
$ kubectl create -f https://operatorhub.io/install/service-binding-operator.yaml
Making sure that Service Binding Operator installed successfully on Kubernetes
-
One way to make sure that the Operator installed properly is to verify that its pod started and is in “Running” state (note that you will have to specify the namespace where you installed Service Binding Operator in earlier step, and the pod name will be different in your setup than what’s shown in below output):
$ kubectl get pods --namespace operators NAME READY STATUS RESTARTS AGE service-binding-operator-6b7c654c89-rg9gq 1/1 Running 0 15m
-
Another aspect to check is output of below command as suggested in the Operator’s installation instruction:
$ kubectl get csv -n operators
If you see the value under
PHASE
column to be anything other thanInstalling
orSucceeded
, please take a look at the pods inolm
namespace and ensure that the pod starting with the nameoperatorhubio-catalog
is inRunning
state:$ kubectl get pods -n olm NAME READY STATUS RESTARTS AGE operatorhubio-catalog-x24dq 0/1 CrashLoopBackOff 6 9m40s
If you see output like above where the pod is in
CrashLoopBackOff
state or any other state other thanRunning
, delete the pod (note that exact name of the pod will be different on your cluster):$ kubectl delete pods -n olm operatorhubio-catalog-x24dq