This documentation tells you about Tanzu Cloud Service Broker for Azure.

Overview

The Tanzu Cloud Service Broker for Azure enables platform operators to easily expose services to their developers from Azure with an Infrastructure as Code (IaC) approach. Cloud Service Broker for Azure is thoroughly extensible, and can expose new services or public clouds through the use of custom brokerpaks that rely on OpenTofu providers.

Key Features

Cloud Service Broker for Azure includes the following key features:

  • Easily extensible and maintainable: Cloud Service Broker for Azure uses brokerpaks to expose services. If your target public cloud has a OpenTofu provider, you can provision services through a common interface using standard Cloud Foundry CLI (cf CLI) commands. For more information about brokerpaks, see Brokerpak Introduction in GitHub.
  • One common broker for all brokered services: Cloud Service Broker for Azure decouples the service broker functionality from the catalog of services that it exposes.
  • CredHub integration out-of-the-box: CredHub encrypts and manages all the secrets associated with your usage of cloud services.
  • Community: When you expose a service through a brokerpak, you can make it available to everyone who uses Cloud Service Broker for Azure and vice versa. For more information, see the Brokerpak Introduction in GitHub.

Product Snapshot

The following table provides version and version-support information about Cloud Service Broker for Azure.

Element Details
Tile version 1.9.0
Release date June 10, 2024
Software component version 1.9
Compatible Ops Manager versions 2.10.33 and later
Compatible VMware Tanzu Application Service for VMs version 2.11 and later
Compatible VMware Tanzu Application Service for VMs [Windows] version 2.11 and later
IaaS support Azure

Requirements

Cloud Service Broker for Azure has the following requirements:

  • Access to the Azure console
  • VMware Tanzu Application Service for VMs (TAS for VMs) installed on your platform of choice

Limitations

Cloud Service Broker for Azure has the following limitations:

  • Currently the broker can only be extended to additional IaaS or services by pulling the broker from GitHub. The tiles do not support custom brokerpaks at this time.
  • Currently the broker does not support cross-IaaS provisioning of service instances.

Feedback

If you have a feature request, questions, or information about an issue, please open an issue on the cloud-service-broker or csb-brokerpak-azure GitHub repositories or post in the #cloudservicebroker Cloud Foundry Slack channel.

check-circle-line exclamation-circle-line close-line
Scroll to top icon