Release notes for Cloud Service Broker for GCP

Last Updated October 24, 2024

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

v1.4.0

Release Date: February 8, 2024

This release has no breaking changes.

This release has the following new features:

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 GCP.
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.

This release has the following fixes:

Prevent performance degradation of database consistency checks at startup

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

Inconsistency in Credential Naming Conventions: There is a known issue affecting Spring applications that use autoconfiguration with spring-cloud-gcp-starter-storage and spring-cloud-gcp-cloudfoundry dependencies. These applications encounter difficulties when attempting to connect to Google Storage because the Cloud Service Broker (CSB) for GCP exposes GCP credentials under project_id and private_key_data, whereas the expected fields in the VCAP services JSON are ProjectId and PrivateKeyData. Additionally, the required service tag google-storage is absent, which may further disrupt proper service detection and configuration.

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