Release Notes for Cloud Service Broker for GCP

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

v1.3.1

Release Date: December 20, 2023

This release has the following fix:

The preinstall check does not run on reconfiguration:

Previously, the preinstall check correctly ran before attempting an upgrade but incorrectly ran when reconfiguring the tile. This blocked configuration changes needed to resolve potential upgrade issues.

Release Date: November 1, 2023

This release has the following breaking changes:

The Tanzu Cloud Service Broker for GCP tile stops the installation if there are any outdated instances:

From now on, ensure that service instances are up to date before upgrading the tile. Out-of-date service instances cause the installation to stop. Your instances use the latest released features that include the latest security patches.
The Tanzu Cloud Service Broker for GCP tile now requires Jammy Stemcell: The tile depends now on Jammy Stemcells instead of Xenial. You must have a Jammy Stemcell available in Tanzu Operations Manager, and you must be using Tanzu Operations Manager v2.10.33 or later.

New features and changes in this release.

Postgres 15 is now supported: You can now create and bind to instances with version 15 of PostgreSQL.
postgres_version: This field is no longer a hard-coded closed set. You can now specify any version exposed by GCP.

Caution You must use caution when adopting a version of PostgreSQL that is not yet officially supported by Cloud Service Broker for GCP. VMware might take time to validate whether a new version of PostgreSQL is fully compatible with Cloud Service Broker for GCP. To learn whether a specific version of Postgres is officially supported or not, refer to the release notes.
High availability configuration: You can now turn on high availability for an instance by using the highly_available property. When enabled, this deploys two instances, primary and standby, in different zones of instance’s region. If needed, you can specify concrete zones by using the location_preference_zone and location_preference_secondary_zone parameters. You can turn high availability on or off, or re-assign the zone at any time. For more information on PostgreSQL high availability, see the Google Cloud documentation.

This release has the following fixes:

Fixes a timeout when starting the app: In some scenarios, the application takes longer than 60 seconds to start. This causes Cloud Foundry to mark the app as unhealthy. To resolve the issue, the timeout for this tile is now 120 seconds.
Improved stack selection to try with “cflinuxfs3” before using the default value:

Previously, in some scenarios, the default value was a Windows stack, which caused the tile installation to fail.

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.