CloudSQL Internal IP does not belong to connected network subnet range

[kronus86]

Hello Experts,

I have recently done a VPC setup where Subnet range for "us-central1" is 

us-central1

IPv4

10.128.0.0/20

None

However when I configured my CloudSQL to be part of this network the IP it got does not belong to the above subnet range.

PostgreSQL

10.123.224.10

Can you please suggest why this is happening.

Thanks for the help.

[kronus86]

This is blocking Access to the database via VPC peering. This is because it complains about not finding any Subnet for the IP address in the peered network. Any help is appreciated on how to get access the this database via peering.

[kronus86 · Accepted solution]

It seems when we enable private IP for a database a new subnet gets created for "Private Service Access" for the database which does not get advertised by default.