In the google cloud docs it is clearly stated that connectivity to Cloud SQL using private IP can be established across regions, however it's not what I see at the moment. private access was enabled, but I still cannot connect to the instance in the West1 region. Firewall rules are the same for both regions. Routes for peering networks are autocreated but have different descriptions:
And have different corresponding next hops, which I didn't see stated anywhere in the docs as well. Can someone shed some light on this issue?
Firewalls out are enabled for all the destinations.
First one connects fine:
Second one timeouts (in a different region):
Reproduced the same behavior on the empty project with newly created VPC.
I tried the experiment with other service which requires private service access: MemoryStore with Redis but for this services it is clearly stated that client must be in the same region as the instance to call it, so should I presume it is a typo in the Cloud Sql documentation?
I found the contradiction in the google docs for Cloud SQL, the direct specific documentation for Cloud SQL and the generic documentation about private service access, can someone confirm which option is valid?
Here it says otherwise: