The Operator Framework provides support for Kubernetes-native extensions to manage custom resource types through operators. Many operators are available through operatorhub.io, including the IBM Cloud operator. The IBM Cloud operator simplifies the creation of IBM Cloud services and resouces and binding credentials from these resources into a Kubernetes cluster. The instructions in this guide are adapted from the IBM Developer tutorial Simplify the lifecycle management process for your Kubernetes apps with operators.
The steps in this guide require execution by a user with cluster-admin role. If you are using Minishift, be sure to enable the admin-user addon and then log in to the oc cli using this user:
oc login -u admin -p the-admin-passwd
Begin by applying the Operator Lifecycle Manager (OLM) release to your cluster:
oc apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/crds.yaml
oc apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.10.0/olm.yaml
Before continuing, check to ensure that the pods in the olm namespace have started. This can take a few minutes for the container images to be pulled and the pods to start.
oc get pods --namespace olm
NAME READY STATUS RESTARTS AGE
catalog-operator-6bb8ffd7c5-4jwwz 1/1 Running 0 2m
olm-operator-78ff5d69cf-2ssbs 1/1 Running 0 2m
olm-operators-ts4h4 1/1 Running 0 1m
operatorhubio-catalog-q2kwj 1/1 Running 0 1m
packageserver-567b8d96b7-d75vp 1/1 Running 0 11s
packageserver-567b8d96b7-hlx8g 0/1 Running 0 11s
Next, to install the Marketplace Operator (allows for adding operators from the operator marketplace) perform these steps from a folder/directory outside of the guestbook-openshift repository folder:
git clone https://github.com/operator-framework/operator-marketplace.git
oc apply -f operator-marketplace/deploy/upstream/
Now, configure a namespace for the marketplace operators
oc apply -f - <<END
apiVersion: operators.coreos.com/v1alpha2
kind: OperatorGroup
metadata:
name: marketplace-operators
namespace: marketplace
END
At this point, you should be able to install any operator from the operatorhub.io marketplace.
Continue with these steps with the same user logged into the cluster. With the OLM framework and marketplace support installed, it's time to install the IBM Cloud operator. This operator will use an IBM Cloud API key to manage resources within the cluster. Begin to configure the IBM Cloud operator by logging in to the IBM Cloud account using the IBM Cloud CLI.
ibmcloud login
In order to be able to provision Cloud Foundry services, choose the correct Org and Space for the IBM Cloud account (this will choose a default Org and Space if there is only one available in the account. Otherwise it will prompt )
ibmcloud target --cf
Check the outpuit from the ibmcloud target command. If there is no resource group set, resulting in a message including:
Resource group: No resource group targeted, use 'ibmcloud target -g RESOURCE_GROUP'
then set the target resource group to the Default using:
ibmcloud target -g Default
Use the script from the IBM Cloud operator repository to create the API key and add it as a secret to the default project on Minishift:
This command requires curl and bash. For Windows 10, they can be configured by either setting up git bash or the Windows Subsystem for Linux.
curl -sL https://raw.githubusercontent.com/IBM/cloud-operators/master/hack/config-operator.sh | bash
The operator marketplace catalog provides a URL for the resources to install for each operator. Install the IBM Cloud Operator with the following command:
oc create -f https://operatorhub.io/install/ibmcloud-operator.yaml
Check that the pod for the IBM Cloud operator is running:
$ oc get pods --namespace operators
NAME READY STATUS RESTARTS AGE
ibmcloud-operator-7dd98d9754-lphll 1/1 Running 0 1mYour cluster now has the IBM Cloud operator installed. This operator is able to configure two kinds in the cluster, a Service and a Binding. The Service defines a specific IBM Cloud service instance type to create, and the Binding specifies a named binding of a service instance to a secret in the cluster. For more details about the IBM Cloud operator see the project repository
Continue by using the IBM Cloud operator to Create a Tone Analyzer service on IBM Cloud