Tanzu Cloud Service Broker for Microsoft Azure 1.7

1.12 1.11 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 1.2 1.1 1.0

Release notes for Cloud Service Broker for Azure

Last Updated October 24, 2024

This topic describes the changes in this minor release of Tanzu Cloud Service Broker for Azure (Cloud Service Broker for Azure).

v1.7.0

Release date: February 8, 2024

Breaking changes

This release has the following breaking changes:

  • The Tanzu Cloud Service Broker for Azure tile now requires Jammy Stemcell:

    The tile now depends on Jammy Stemcells instead of Xenial. You must have a Jammy Stemcell available in Tanzu Operations Manager, and Tanzu Operations Manager must be at version v2.10.33 or later.

Features

New features and changes in this release:

General

  • Terraform upgraded to v1.5.7:

    The Terraform version used to apply changes is upgraded to v1.5.7. You must upgrade all service instances. When you upgrade, ensure that you follow the Upgrade procedure.

  • Apply changes now fails if there were problems upgrading one or more instances:

    Issues when upgrading instances are now surfaced to Tanzu Operations Manager by failing the deploy-all errand. In this case, the deployment log needs to be inspected for detailed information on upgrade failures. For more information on the upgrade process, see Upgrading Cloud Service Broker for Azure.

  • Tile installation now does not install if it finds any outdated non-orphaned instances:

    This measure improves the overall stability and maintainability of the broker and any running instances. It protects operators from accidentally skipping mandatory intermediate versions, which could introduce unexpected issues. Despite this measure, VMware expects operators to harness Upgrade Planner to view the supported upgrade path.

Resolved issues

This release has the following fixes:

  • Prevent performance degradation of database consistency checks at startup

    Previously the Cloud Service Broker for Azure kept information in the database about instances and bindings that had already been destroyed. In the long term, this caused Cloud Service Broker’s database space usage to grow with no real benefit. In some rare scenarios, this made Cloud Service Broker start up slower and caused the platform to timeout. The Cloud Service Broker for Azure now physically deletes information from destroyed assets, preventing this situation from happening.

Known issues

This release has no known issues.

View release notes for another version

To view the release notes for another product version, select the version from the drop-down menu at the top of this page.