CuraDevOps

tag: Cloud-Sql · 4 items

2026-10-24 · GCP Release Notes · source ↗ #gcp#cloud-sql#security
  • Platform/SRE — Plan: Teams using Cloud SQL Auth Proxy must upgrade to 2.26.3+, Cloud SQL Proxy Operator to 1.8.4+, and Ops Agent to 2.73.0 to address this Go root-certificate vulnerability (GCP-2026-071); managed Cloud SQL instances are auto-patched during scheduled maintenance. CVE is not KEV-listed and EPSS is 0.00, so no active exploitation warrants immediate emergency action, but proxy upgrades are concrete tasks to schedule this sprint.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: CVE-2026-111943 — CISA KEV: not listed, EPSS 0.00
2026-09-18 · GCP Release Notes · source ↗ #gcp#cloud-sql#compute-engine
  • Platform/SRE — Plan: Cloud SQL (MySQL and PostgreSQL) now auto-enables PITR after DR switchover/failover asynchronously, reducing RTO — review your DR runbooks to reflect the faster recovery path. The GA Z4D machine series (AMD EPYC Turin, up to 3 TB local storage) is worth evaluating this quarter for storage-heavy workloads like databases, search, or vector stores.
  • CI/CD — Skip
  • Leader — Learn: The Z4D GA instances and Cloud SQL PITR improvements are worth noting for teams standardizing on GCP for storage-heavy or analytics workloads, but neither forces a strategic decision or pricing change now.
  • Signals: GA announcement
2026-08-26 · GCP Release Notes · source ↗ #cloud-sql#gcloud-sdk#breaking-change
  • Platform/SRE — Plan: Cloud SQL Proxy V1 (‘cloud_sql_proxy’) is removed from gcloud SDK 582.0.0 — audit infrastructure automation and connection scripts for V1 references and migrate to ‘cloud-sql-proxy’ V2 before upgrading gcloud to 582.0.0.
  • CI/CD — Plan: If pipelines use gcloud to establish Cloud SQL connections or reference the removed api-registry MCP commands, they will break on upgrade to gcloud 582.0.0 — audit pipeline scripts and update to Cloud SQL Auth Proxy V2 before rolling out the new SDK version.
  • Leader — Skip
  • Signals: breaking-change flagged
  • Platform/SRE — Plan: Two GA releases are worth scheduling for adoption: native OTLP metric ingestion into Cloud Monitoring via the Telemetry API (evaluate replacing or supplementing existing collector pipelines), and Cloud SQL for MySQL performance capture with configurable thresholds for long-running transactions and new triggers like CPU, memory, and lock waits.
  • CI/CD — Skip
  • Leader — Learn: The Telemetry API GA enables native OTLP ingestion into Cloud Monitoring, which may affect the build-vs-buy decision for third-party observability tooling on GCP; no strategic decision is required yet.
  • Signals: GA announcement