How can I ensure cloud-sql-proxy sidecar container is running before other containers connecting to cloudsql from k8s? about cloud-sql-proxy

[chardch]

Got it, thank you for this info! The wait command is exactly what I was looking for.

[jackwotherspoon]

We recently added support for a wait command #2041 and I think it is what you are looking for.

To help ensure the Proxy is up and ready, this commit adds a wait command with an optional --max flag to set the maximum time to wait.

By default when invoking this command:

./cloud-sql-proxy wait

The Proxy will wait up to the maximum time for the /startup endpoint to respond. This command requires that the Proxy be started in another process with the HTTP health check enabled. If an alternate health check port or address is used, as in:

./cloud-sql-proxy <INSTANCE_CONNECTION_NAME> \
  --http-address 0.0.0.0 \
  --http-port 9191

Then the wait command must also be told to use the same custom values:

./cloud-sql-proxy wait \
  --http-address 0.0.0.0 \
  --http-port 9191

By default the wait command will wait 30 seconds. To alter this value, use:

./cloud-sql-proxy wait --max 10s

@chardch does that work for your use-case?

[enocom]

This works in combination with a poststart hook. Context: https://medium.com/@marko.luksa/delaying-application-start-until-sidecar-is-ready-2ec2d21a7b74

[enocom]

Going to close this. Feel free to reopen if you’re still stuck on this.