3 ms·

Does the move to gVisor pave the way to connecting CloudSQL instances? The removed limitations sound like they were road blocks.

• merb 8y ago
  you already could connect to cloudsql instances. however you needed a proxy, but not because of AppEngine, you need it because of security. either you whitelisted your ips or you used the proxy (which go appengine could already use). so with go you just needed to use https://github.com/GoogleCloudPlatform/cloudsql-proxy https://github.com/GoogleCloudPlatform/cloudsql-proxy which means you just need to change the query string. however a new feature is emerging where you can have a private ip that is connected to your internal services, however it is still a beta feature. Source: myself, but not a googler, just a regular user
  • chrisbroadfoot 8y ago
    Notable, though, that this new runtime better supports connecting to Postgres instances through the unix socket (/cloudsql/). (GCP Gopher)
    • deleted 8y ago
      [deleted]
• buss 8y ago
  For cloudsql in particular, you can connect via the `/cloudsql` Unix socket. But anything that needs raw socket access can now be used from App Engine. See https://cloud.google.com/appengine/docs/standard/go111/using-cloud-sql https://cloud.google.com/appengine/docs/standard/go111/using... and scroll way down to the sample code.
  • selljamhere 8y ago
    Awesome!