The Proxy won't ever send SIGTERM signals. In v2 we've fixed the exit code handling such that the Proxy will exit with a non-zero code if there are still active connections. It sounds like Kubernetes is shutting down your pod (for reasons unknown to me and beyond what the Proxy knows), and the non-zero exit is making things worse.

Here are a few of things to try:

1. Update to latest v2 (currently v2.2.0)
2. Set the max-sigterm-delay to some reasonable value. This will give the app more time to shut down its active connections and possibly result in the Proxy exiting cleanly.
3. And probably less useful but worth knowing about: consider if the quitquitquit flag would help. here.

The Proxy won't ever send SIGTERM signals. In v2 we've fixed the exit code handling such that the Proxy will exit with a non-zero code if there are still active connections. It sounds like Kubernetes is shutting down your pod (for reasons unknown to me and beyond what the Proxy knows), and the non-zero exit is making things worse.

Here are a few of things to try:

1. Update to latest v2 (currently v2.2.0)
2. Set the max-sigterm-delay to some reasonable value. This will give the app more time to shut down its active connections and possibly result in the Proxy exiting cleanly.
3. And probably less useful but worth knowing about: consider if the quitquitquit flag would help. here.

Thanks @enocom for the quick appreciate it very much. We run cloud sql proxy as a side car container so my question is where do I set the max-sigterm-delay is it in the CLI?

@dheerajd3v You just set it as one of your args in your YAML.

name: cloud-sql-proxy
image: "gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.2.0"
args:
- "--private-ip"
- "--port=5432"
- "--max-sigterm-delay=30"

The above will wait 30 seconds for connections to close after receiving a TERM signal.

@dheerajd3v You just set it as one of your args in your YAML.

name: cloud-sql-proxy
image: "gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.2.0"
args:
- "--private-ip"
- "--port=5432"
- "--max-sigterm-delay=30"

The above will wait 30 seconds for connections to close after receiving a TERM signal.

Thanks @jackwotherspoon will make the changes and test. On a different note I also see that there is a Cloud SQL proxy operator in Preview, thoughts on migrating to use this operator instead of the side car pattern? This is the link I am referring to https://cloud.google.com/sql/docs/postgres/connect-proxy-operator. I am not sure why official google docs recommend using a sidecar pattern over the initContainer I am thinking about the race condition what happens if my App container comes up and DB container is still not up?

I am not sure how to do this . This is from GCP official docs

Hi @dheerajd3v

The Cloud SQL Auth Proxy Operator will make it easier to set up proxy sidecar containers for your apps. We expect the operator to be within GA in the next 2 months. Give it a try and let us know if it works for you.

We recommend running the proxy as a sidecar container for two reasons:

• The proxy container and the application container can run at the same time.
• The connection is more secure when the application container connects to the proxy container using the localhost network 127.0.0.1. It is even more secure if the proxy exposes the database as a unix socket. To do this in kubernets, the proxy needs to run in the same pod as the application.

Init containers serve a different purpose than sidecar containers. Init containers must exit before the pod containers start. See Init Containers

Unfortunately, there is no pure Kubernetes way to avoid the race condition when a pod's containers start up. Kubernetes does not allow you to specify a startup order for a pod's containers.

We recommend that you write your app to be resilient to failed database connections. Your app should retry a failed database connection attempt for a reasonable period of time (maybe 30 seconds) before exiting with a failure.

Going to go ahead and close this as I believe the initial question has been answered 😄

If there are any follow-up questions feel free to re-open the issue or create a new issue for the question.

Have a great day and thanks for using the Cloud SQL Proxy.