VMware recommends that you upgrade to the latest patch available for your current minor, and then upgrade to the latest patch available for the next minor.

For product versions and upgrade paths, see Upgrade Planner.

Because VMware uses the Percona Distribution for MySQL, expect a time lag between Oracle releasing a MySQL patch and VMware releasing VMware SQL with MySQL for Tanzu Application Service containing that patch.

VMware SQL with MySQL for Tanzu Application Service 3.1.x is the last version of VMware SQL with MySQL for Tanzu Application Service that supports MySQL 5.7. VMware Tanzu for MySQL 3.2.0 and later only support MySQL 8.0. If you are upgrading from an earlier release of VMware Tanzu for MySQL, you must reconfigure any plans previously configured with "MySQL Default Version" of 5.7 to specify 8.0.
For more information about the upgrade process from 5.7 to 8.0, including items to review to ensure a smooth transition, please see Upgrading from MySQL 5.7 to 8.0.

v3.2.2

Release Date: Jan 15, 2025

Changes

This release includes the following changes:

• Bugfix: Patches MySQL to fix a bug that can lead to increasing memory usage if the audit log plug-in is enabled.
• Bugfix: Backup process can exit successfully during network failures and when the backup is configured incorrectly in Tanzu Operations Manager.
• Bugfix: mysql-diag can run successfully even if the HA cluster is in an unexpected state.
• Feature: Improves logging during the backup process
• Feature: Operators can manually set a property to allow upgrades to continue by using cf upgrade-service in cases when the upgrade might result in manifest changes, such as when upgrading a stemcell.
• Upgrades dependencies, resolves CVEs

Compatibility

The following components are compatible with this release:

* Components marked with an asterisk have been updated

v3.2.1

Release Date: April 8th, 2024

Changes

This release includes the following changes:

• A number of high and critical CVEs are addressed by updating components to the latest version.

Breaking Changes

• MySQL v5.7 is no longer supported.:

Existing service plans that used a “MySQL Default Version” of “5.7” must be updated. Any service instance created with one of these plans will be updated to MySQL 8.0 when the instance is upgraded. For more information about upgrading VMware Tanzu for MySQL, see Upgrading VMware SQL with MySQL for Tanzu Application Service.

Resolved Issues

This release resolves the following issues:

• Binding creation is further isolated from ongoing transaction execution. Previously, binding creation during an active transaction sometimes failed or aborted the transaction.
• Improved recovery of MySQL service instances after a VM reboot.
• The bootstrap errand now self-selects a high-availability cluster instance node on which to run, and no longer requires the --instance flag.

Compatibility

The following components are compatible with this release:

* Components marked with an asterisk have been updated

Known Issues

• A bug within MySQL can lead to increasing memory usage if the audit log plugin is enabled. This is fixed in v3.2.2
• Incorrectly configured backups and network failures can cause the backup process to fail to exit, which leads to increasing memory usage. This is fixed in v3.2.2
• There is a bug with MySQL route flakiness when using this tile version and TAS versions 4.0.27 - 4.0.30, 6.0.7 - 6.0.10, 10.0.0. This is fixed in v3.2.2

v3.2.0

Release Date: February 16th, 2024

This release includes the following changes:

• Multi-site replication can be configured using highly available (HA) leaders.
• Demoted multi-site leaders can be made writable again.
• A number of high and critical CVEs are addressed by updating components to the latest version.

Breaking Changes

• MySQL v5.7 is no longer supported.:

  Existing service plans that used a “MySQL Default Version” of “5.7” must be updated. Any service instance created with one of these plans will be updated to MySQL 8.0 when the instance is upgraded. For more information about upgrading VMware Tanzu for MySQL, see Upgrading VMware SQL with MySQL for Tanzu Application Service.

Resolved Issues

This release resolves the following issues:

• Database objects (stored procedures, functions, views) created by users are still available after those users are deleted. Previously, a user with the same user name needed to be recreated.

Compatibility

The following components are compatible with this release:

* Components marked with an asterisk have been updated

Known Issues

• A bug within MySQL can lead to increasing memory usage if the audit log plugin is enabled. This is fixed in v3.2.2
• Incorrectly configured backups and network failures can cause the backup process to fail to exit, which leads to increasing memory usage. This is fixed in v3.2.2
• There is a bug with MySQL route flakiness when using this tile version and TAS versions 4.0.27 - 4.0.30, 6.0.7 - 6.0.10, 10.0.0. This is fixed in v3.2.2