Integrate with Azure-managed services using Open Service Broker for Azure (OSBA)

Together with the Kubernetes Service Catalog, Open Service Broker for Azure (OSBA) allows developers to utilize Azure-managed services in Kubernetes. This guide focuses on deploying Kubernetes Service Catalog, Open Service Broker for Azure (OSBA), and applications that use Azure-managed services using Kubernetes.


Install Service Catalog

The first step is to install Service Catalog in your Kubernetes cluster using a Helm chart. Upgrade your Tiller (Helm server) installation in your cluster with:

helm init --upgrade

Now, add the Service Catalog chart to the Helm repository:

helm repo add svc-cat

Finally, install Service Catalog with the Helm chart. If your cluster is RBAC-enabled, run this command.

helm install svc-cat/catalog --name catalog --namespace catalog --set --set apiserver.healthcheck.enabled=false --set controllerManager.healthcheck.enabled=false --set apiserver.verbosity=2 --set controllerManager.verbosity=2

If your cluster is not RBAC-enabled, run this command.

helm install svc-cat/catalog --name catalog --namespace catalog --set rbacEnable=false --set --set apiserver.healthcheck.enabled=false --set controllerManager.healthcheck.enabled=false --set apiserver.verbosity=2 --set controllerManager.verbosity=2

After the Helm chart has been run, verify that servicecatalog appears in the output of the following command:

kubectl get apiservice

For example, you should see output similar to the following (show here truncated):

NAME                                 AGE
v1.                                  10m             10m
...        34s               10

Install Open Service Broker for Azure

The next step is to install Open Service Broker for Azure, which includes the catalog for the Azure-managed services. Examples of available Azure services are Azure Database for PostgreSQL, Azure Database for MySQL, and Azure SQL Database.

Start by adding the Open Service Broker for Azure Helm repository:

helm repo add azure

Create a Service Principal with the following Azure CLI command:

az ad sp create-for-rbac

Output should be similar to the following. Take note of the appId, password, and tenant values, which you use in the next step.

  "appId": "7248f250-0000-0000-0000-dbdeb8400d85",
  "displayName": "azure-cli-2017-10-15-02-20-15",
  "name": "http://azure-cli-2017-10-15-02-20-15",
  "password": "77851d2c-0000-0000-0000-cb3ebc97975a",
  "tenant": "72f988bf-0000-0000-0000-2d7cd011db47"

Set the following environment variables with the preceding values:


Now, get your Azure subscription ID:

az account show --query id --output tsv

Again, set the following environment variable with the preceding value:

AZURE_SUBSCRIPTION_ID=[your Azure subscription ID from above]

Now that you've populated these environment variables, execute the following command to install the Open Service Broker for Azure using the Helm chart:

helm install azure/open-service-broker-azure --name osba --namespace osba \
    --set azure.subscriptionId=$AZURE_SUBSCRIPTION_ID \
    --set azure.tenantId=$AZURE_TENANT_ID \
    --set azure.clientId=$AZURE_CLIENT_ID \
    --set azure.clientSecret=$AZURE_CLIENT_SECRET

Once the OSBA deployment is complete, install the Service Catalog CLI, an easy-to-use command-line interface for querying service brokers, service classes, service plans, and more.

Execute the following commands to install the Service Catalog CLI binary:

curl -sLO$(uname -s)/$(uname -m)/svcat
chmod +x ./svcat

Now, list installed service brokers:

./svcat get brokers

You should see output similar to the following:

  NAME                               URL                                STATUS
  osba   http://osba-open-service-broker-azure.osba.svc.cluster.local   Ready

Next, list the available service classes. The displayed service classes are the available Azure-managed services that can be provisioned through Open Service Broker for Azure.

./svcat get classes

Finally, list all available service plans. Service plans are the service tiers for the Azure-managed services. For example, for Azure Database for MySQL, plans range from basic50 for Basic tier with 50 Database Transaction Units (DTUs), to standard800 for Standard tier with 800 DTUs.

./svcat get plans

Install WordPress from Helm chart using Azure Database for MySQL

In this step, you use Helm to install an updated Helm chart for WordPress. The chart provisions an external Azure Database for MySQL instance that WordPress can use. This process can take a few minutes.

helm install azure/wordpress --name wordpress --namespace wordpress --set resources.requests.cpu=0 --set replicaCount=1

In order to verify the installation has provisioned the right resources, list the installed service instances and bindings:

./svcat get instances -n wordpress
./svcat get bindings -n wordpress

List installed secrets:

kubectl get secrets -n wordpress -o yaml

Next steps

By following this article, you deployed Service Catalog to an Azure Kubernetes Service (AKS) cluster. You used Open Service Broker for Azure to deploy a WordPress installation that uses Azure-managed services, in this case Azure Database for MySQL.

Refer to the Azure/helm-charts repository to access other updated OSBA-based Helm charts. If you're interested in creating your own charts that work with OSBA, refer to Creating a New Chart.