At the time of writing this KB AWS RDS using MYSQL engine 8.0 will reach end of standard Support on July 31 2026. This KB will help answer frequently ask questions related to RDS upgrades and compatibility with Tanzu Foundation Core ( Also known as Tanzu Operations manger) and Elastic Application Runtime ( also known as Tanzu Platform Application Service )
Refer to AWS RDS instance version dates page for end of support information.
We do not maintain or publish a compatibility matrix for AWS RDS instances. While we do test with MySQL external databases internally we do not test all variants from each individual cloud provider. We do expect the selected MySQL provider will be compliant and compatible with Operations Manager and Elastic Application Runtime. Should a compatibility issue surface we will tree it as a bug and address accordingly
We have manually tested this version internally along with a migration from 8.0 to 8.4 and there are no known compatibility issues
Yes there will be some degree of downtime during the upgrade process. The symptoms for each component are explained below
The BOSH Director will return 500 errors and other API errors while the database instance is being upgraded. Operations Manager will show status errors in the Director Tile status page. These errors will self heal once the database upgrade is complete.
Platform APIs may not be available during the procedure, see the specific details below. These symptoms will self heal once the RDS instance completes its upgrade
Users will not be able to log in during the migration.
cf ssh, push, start, stop etc.. commands will not function while the database is down for upgrade.
It is unlikely that applications need access at runtime (after startup) to CredHub. Applications that depend on CredHub may be unable to restart during the migration.
Autoscaling is going to be paused
Standard configurations of TAS should not experience any application downtime during the upgrade. Diego Cells and edge routers are not affected by the database upgrades and therefore, applications already running should remain running and routable.
Because implicit and auth code grants do not work without database access, users of SSO-based apps will not be able to create new sessions. This would likely cause these types of applications to experience downtime.