This page describes the extended support policy for Cloud SQL.
Google Cloud offers extended support for Cloud SQL for MySQL major versions that reach end-of-life (EOL) by the developer community.Overview
During extended support, Cloud SQL instances receive the following:
- Security fixes: Patches for critical security bugs.
- Bug fixes: Resolution of bugs in Cloud SQL-maintained code.
- Service Level Agreement (SLA) coverage: Edition-specific coverage for instances that meet the eligibility criteria as documented in the SLA.
- Support for new instance creation: Ability to create new Cloud SQL instances that use major versions in extended support.
For a complete list of supported Cloud SQL database versions and their stages in the support lifecycle, see Major and minor versions supported by Cloud SQL.
For most major versions, extended support starts within three months of the major version reaching its EOL by the developer community. At that time, any Cloud SQL instance running a Cloud SQL for MySQL major version that's EOL is enrolled in extended support automatically.
Extended support is a paid service. Although instances are enrolled automatically, you can opt out at any time by upgrading your instance to a major version that's covered by Cloud SQL regular support. To enroll in extended support and keep your instance on the same major version, you don't need to do anything.
Pricing
Pricing details for extended support are available on the Cloud SQL pricing page.
How to opt out
You can opt out of extended support at any time by upgrading your instance to a major version in regular support.
Deprecation
Extended support for a major version is available for three years. After three years, the major version is deprecated.
For more information about deprecation in Cloud SQL, see Deprecation.
Recommendations
To keep up with regular support, we recommend that you upgrade to the default major version of your database engine. For Cloud SQL for MySQL, upgrade to the latest major version and the default minor version.
In addition, we also recommend that you test the major version upgrade thoroughly in a non-production environment to ensure that any changes to the major version don't impact your applications. To do so, you can use one of the several methods that Cloud SQL provides to create a copy of the instance and upgrade the instance to the newer major version.
For more information about performing a major version upgrade, see Upgrade the database major version in-place and Upgrade the database major version by migrating data.