Can you please describe steps to reproduce? Like how you are setting up OneDev with postgres instance, and how you are closing OneDev, etc.

The database is set up with the helm through the database settings in the values.yaml. When a new version is available, a SIGTERM signal is sent to OneDev as part of the helm upgrade command.

Lifecycle

I assume that here the database connection are not terminated successfully, bceause when the new instance tries to connect to Postgres, the application fails with the reason, that there are no more non-administration connection available.

Tried with below procedure but can not reproduce:

1. Create a new k8s cluster at GKS

2. Run below command to deploy PostgreSQL and OneDev 11.6.10:

   kubectl create namespace onedev
   helm install mypostgres bitnami/postgresql --namespace onedev
   kubectl get secret --namespace onedev mypostgres-postgresql -o jsonpath="{.data.postgres-password}"|base64 --decode
   helm install onedev onedev/onedev -n onedev --set database.external=true --set database.type=postgresql --set database.host=mypostgres-postgresql --set-string database.port=5432 --set database.name=onedev --set database.user=postgres --set database.password=<decoded password from previous command> --set image.tag=11.6.10
   

3. Access OneDev UI to set up the server and add a test project

4. Run below command to upgrade OneDev to 11.6.16:

   helm upgrade onedev onedev/onedev -n onedev --set image.tag=11.6.16 --reuse-values
   

After OneDev up and running after upgrade, check the opened database connections of postgresql, and it is still 25 (which is the default).

Thank you for the reply and help.

Okay - then I am not sure what is happening. I'll just make sure to close all database connections manually before updating. This has been the approach so far, so it should be fine.

Thanks again!