cloud-sql-go-connector: Connection failure due to Cloud SQL Admin API per user/minute quota

Hi,

we’re experiencing an issue with the go connector that I just can’t make sense of. At some point, we hit the Cloud SQL Admin API per user/minute quota (in our case 180) for no apparent reason. Of course, once the quota is reached, refresh attempts do not succeed and no connection to cloudsql can be established, because the calls to google.cloud.sql.v1beta4.SqlConnectService.GenerateEphemeralCert and google.cloud.sql.v1beta4.SqlConnectService.GetConnectSettings fail with a 429 error. The only way to resolve this seems to be to kill the deployment for at least 1 minute, so that the quota resets. Then everything is fine again, but who know for how long. We use IAM authentication and authorization. The service account is only used for one service, so the api calls all originate from that one specific service using the cloud-sql-go-connector.

Has anyone else experienced this kind of behavior?

Thanks!

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 1
  • Comments: 18 (9 by maintainers)

Commits related to this issue

Most upvoted comments

You’ll want to call cleanup when you’re done with the connector because it does stop all background refreshes.