Why it matters
The surcharge buys nothing new: it only pays for running an old version longer. Upgrading removes it and keeps the database on a version that gets fixes.How nOps finds it
nOps looks for Cloud SQL usage lines whose description mentions extended support. An instance is flagged when it was billed the surcharge in the last 2 days. The saving is the surcharge itself over the last 7 days, scaled to a month, net of discounts and excluding credits, and must be at least $10 a month. Surcharge lines billed at $0 are left out. Projects whose spend on the service is at least 90% paid by credits or promotions are left out.Before you start
A tested upgrade path for your application to the target major version, and a recent backup.How to implement
- Check which major versions are in standard support and pick a target version.
- Test the application against the new version, ideally on a clone of the instance.
- Take an on-demand backup.
- Run an in-place major version upgrade in a maintenance window: in the console, open the instance and choose Edit → Upgrade, or run
gcloud sql instances patch INSTANCE --database-version=TARGET_VERSION. - Update the version in Terraform so the next deployment does not try to change it back.
Risks and considerations
- A major version upgrade restarts the instance and can change query behavior, so test first.
- It cannot be rolled back in place. To go back, restore the backup taken before the upgrade to a new instance.
- Read replicas may need to be upgraded or recreated as part of the process.
FAQs
Is the saving the whole cost of the instance?
Is the saving the whole cost of the instance?
No. It is only the extended support surcharge. The rest of the instance cost stays.