RDI: Document Google Cloud SQL for MySQL as a source

[ZdravkoDonev-redis]

What this adds

• New page prepare-dbs/gcp-cloud-sql-mysql.md (Prepare Google Cloud SQL for MySQL for RDI), scoped to self-managed RDI (VM or Kubernetes). It covers:
  • Enabling binary logging (--enable-bin-log, or point-in-time recovery in the console).
  • Setting the binlog_row_image database flag. The value must be lowercase full, because Cloud SQL rejects FULL.
  • Checking the binlog variables, and authorizing the RDI egress IP in authorized networks.
  • Creating the CDC user with gcloud sql users create --host=%, plus the ERROR 1410 that appears when the user's host doesn't match the GRANT.
  • Setting database.ssl.mode: required under advanced.source when Cloud SQL enforces encrypted connections. Without it, deployment fails with a misleading Access denied ... (using password: YES).
  • What to expect during a Regional HA failover.
• A short note on the MySQL/MariaDB preparation page that links to the new page, next to the existing Amazon RDS note.

The supported-versions embed already lists MySQL 8.0 under "GCP SQL Versions", so it isn't changed.

Basis

This is based on hands-on testing of self-managed RDI 2.0.0 (Debezium collector, Flink processor) on a VM against a new Cloud SQL for MySQL 8.0 instance (8.0.45-google). The instance used Regional HA, a public IP with authorized networks, and sslMode=ENCRYPTED_ONLY. Snapshot, CDC insert/update/delete, and gcloud sql instances failover during active writes all passed. During failover, RDI reconnected on its own and caught up with about one minute of extra lag. No committed changes were missed.

Not tested, so not documented

• RDI on Redis Cloud (the managed service still lists AWS-hosted sources only).
• Cloud SQL for MySQL versions other than 8.0, read replicas, and cross-region replicas.
• Private IP, Private Service Connect, and the Cloud SQL Auth Proxy.
• database.ssl.mode: verify_ca/verify_identity with the Cloud SQL server CA. The page points to the existing TLS section for this but doesn't claim it was validated.
• Tuning the post-failover detection delay. The likely knob is the Debezium MySQL connect.keep.alive.interval.ms property through advanced.source.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only changes with no runtime, security, or data-path code modifications.

Overview
Adds Prepare Google Cloud SQL for MySQL for RDI, a new integration doc for self-managed RDI (VM/Kubernetes) that walks through Cloud SQL–specific setup instead of editing my.cnf: enabling binlog (including console/PITR), setting binlog_row_image=full via database flags, validating binlog variables, authorizing RDI egress IPs, creating/granting the CDC user (including ERROR 1410 host mismatches), and configuring database.ssl.mode when connections must be encrypted. It also documents Regional HA failover behavior (automatic RDI reconnect and expected CDC lag).

The existing Prepare MySQL/MariaDB page gains a note beside the RDS callout that points readers to this page for Cloud SQL binlog configuration.

^{Reviewed by Cursor Bugbot for commit f940ca5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Staging links:
https://redis.io/docs/staging/rdi-cloud-sql-mysql-source/integrate/redis-data-integration/data-pipelines/prepare-dbs/gcp-cloud-sql-mysql/
https://redis.io/docs/staging/rdi-cloud-sql-mysql-source/integrate/redis-data-integration/data-pipelines/prepare-dbs/my-sql-mariadb/

[github-actions]

🧠 Redis Memory

Found 7 related items from repository history (2 new this commit):

• PR — Document Supabase support for RDI

  What changed

• PR — DOC-6878 Expand RDI FAQ CDC section with all supported databases

  What

• PR — DOC-6833: Fix four RDI Cloud doc issues from #rdi-cloud

  • Remove Active-Active from the 'multiple targets' use case sentence; add it as an explicit unsupported target topology under 'When not to u

• Commit — DOC-6878 Expand RDI FAQ CDC section with all supported databases

  DOC-6878 Expand RDI FAQ CDC section with all supported databases

• PR — DOC-6475 updated RDI supported sources

  This is the latest info for Debezium 3.4. Let me know if the AWS/GCP product versions also need to be updat

• Commit — RDI: Document Google Cloud SQL for MySQL as a source 🆕

  RDI: Document Google Cloud SQL for MySQL as a source

• PR — DOC-6573 RDI source prep updates for SQL Server on Azure 🆕

  References info in this ticket and the [Microsoft Azure CDC guide](https://learn.microso

Memory updated at f940ca5

[andy-stark-redis]

A few minor optional suggestions, but otherwise LGTM.