This topic describes how to upgrade Tanzu Cloud Service Broker for Azure.

Upgrading to v1.3

Cloud Service Broker for Azure uses Terraform internally to manage the deployment of service instances. Terraform was updated from v0.12 to v1.1. As a result, there is an upgrade process that must be performed on every service instance so that Cloud Service Broker for Azure can continue to manage it.

VMware recommends that you back up service instances before upgrading.

VMware recommends that you review the known issues before upgrading to v1.3. For more information, see Known Issues.

Operators can choose how the upgrade is performed:

  • By default, the tile installation automatically upgrades all service instances. You can deactivate this to have more control of the upgrade process.

  • To upgrade services instances individually, use the command cf upgrade-service for cf CLI v8 and later, or cf update-service --upgrade for cf CLI v7 and earlier.

  • To upgrade all service instances manually, use the cf CLI plug-in UpgradeAllServices. Use this in combination with the command cf upgrade-service. For more information, see Use the Upgrade All Services Plugin.

Use the Upgrade All Services Plug-in

The Upgrade All Services Plug-in is a Cloud Foundry Community plug-in for the cf CLI. It enables you to upgrade more than one service instance at the same time. It detects which service instances have an upgrade pending, and attempts to upgrade them all. If a service instance has already been upgraded, it does not attempt to upgrade it again.

To upgrade service instances using the Upgrade All Services Plug-in:

  1. To install the plug-in, run:

    cf install-plugin UpgradeAllServices
    
  2. Check which instances still need to be upgraded by running:

    cf upgrade-all-services BROKER-NAME -dry-run
    

    Where BROKER-NAME is the name of the Cloud Service Broker for Azure broker you can detect by running cf service-brokers.

  3. Upgrade all instances that have an upgrade pending by running:

    cf upgrade-all-services BROKER-NAME
    

Issues with Upgrading Service Instances to v1.3

In some previous versions of Cloud Service Broker for Azure, incompatible changes were made that prevent upgrading certain service instances to v1.3.

The following services are affected.

Azure Cosmos DB API for MongoDB (csb-azure-mongodb)

If a csb-azure-mongodb service instance was created with v1.1.0 or earlier, upgrading fails. The specific version that created the csb-azure-mongodb instance matters, and it does not matter if a more recent version of Cloud Service Broker for Azure is currently installed.

Azure SQL Database (csb-azure-mssql-db)

If a csb-azure-mssql-db service instance was created with v1.1.6 or earlier, upgrading fails. The specific version that created the csb-azure-mssql-db instance matters, and it does not matter if a more recent version of Cloud Service Broker for Azure is currently installed.

Azure SQL Failover Group (csb-azure-mssql-failover-group)

If a csb-azure-mssql-failover-group service instance was created with v1.1.0 or earlier, upgrading fails. The specific version that created the csb-azure-mssql-failover-group instance matters, and it does not matter if a more recent version of Cloud Service Broker for Azure is currently installed.

Azure SQL Failover Group on Existing Server Pairs (csb-azure-mssql-db-failover-group)

If a csb-azure-mssql-db-failover-group service instance was created with v1.1.6 or earlier, upgrading fails. The specific version that created the csb-azure-mssql-db-failover-group instance matters, and it does not matter if a more recent version of Cloud Service Broker for Azure is currently installed.

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