# Trouble connecting to Cloud SQL Postgres from Temporal Helm on GKE

**URL:** <https://community.temporal.io/t/trouble-connecting-to-cloud-sql-postgres-from-temporal-helm-on-gke/18366>\
**Category:** Server Deployment\
**Created:** [September 18, 2025, 2:26pm UTC](https://community.temporal.io/t/trouble-connecting-to-cloud-sql-postgres-from-temporal-helm-on-gke/18366 "2025-09-18T14:26:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alipqb](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/alipqb/32/7780_2.png) [@alipqb](https://community.temporal.io/u/alipqb)\
**Post date:** [September 18, 2025, 2:26pm UTC](https://community.temporal.io/t/trouble-connecting-to-cloud-sql-postgres-from-temporal-helm-on-gke/18366/1 "2025-09-18T14:26:39Z")

</div>

Hi everyone,

I’m trying to deploy Temporal on GKE using the temporal-helm chart, but I’m running into database connection issues.

I’m using **Google Cloud SQL (Postgres)** with its **private IP address** (not using `cloudsql-proxy`). Following the Temporal Helm guide for Postgres, I successfully created the required schemas/tables for both the persistence and visibility databases.

However, when I deploy Temporal, I get the following error:

> sql schema version compatibility check failed: unable to read DB schema version keyspace/database: temporal error: no usable database connection found.

When I exec into one of the Temporal pods, I can connect to the database manually using the same credentials, so network access and authentication seem fine.

Here’s the relevant part of my Helm values:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/c/cfdafbb0499ac7143629ba873fcde28586f32193.png)

**Question:**  
Has anyone successfully connected Temporal Helm on GKE directly to a Cloud SQL Postgres instance over private IP?  
Am I missing something in the Helm values (e.g., the way `existingSecret` is referenced, or the `postgresql.enabled` flag when using an external database)?

Thanks!

---

<div class="post-metadata">

**Author:** ![beverts312](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/beverts312/32/8152_2.png) [@beverts312](https://community.temporal.io/u/beverts312)\
**Post date:** [January 14, 2026, 4:48pm UTC](https://community.temporal.io/t/trouble-connecting-to-cloud-sql-postgres-from-temporal-helm-on-gke/18366/2 "2026-01-14T16:48:52Z")

</div>

I am also experiencing this.  
The schema job container connects successfully runs the setup but no other containers can connect