Error while upgrading Airbyte helm chart with SSL off for Temporal

Summary

When upgrading Airbyte helm chart to version 0.544.0, encountering errors related to SSL not being enabled on the server for Temporal. User is looking for a way to specify SSL off in the Helm chart for Temporal.


Question

Hi ,
I need your help , while upgrading Airbyte helm chart “0.544.0” , I am getting error on temporal , worker load-launcher & server pods

Is there any way where in Helm chart in Temporal we specify to keep ssl off

sql schema version compatibility check failed: pq: SSL is not enabled on the server
Unable to create server. Error: could not build arguments for function "<http://go.uber.org/fx|go.uber.org/fx>".(*module).constructCustomLogger.func2 (/go/pkg/mod/go.uber.org/fx@v1.20.0/module.go:251): failed to build fxevent.Logger: could not build arguments for function "<http://go.temporal.io/server/temporal|go.temporal.io/server/temporal>".init.func8 (/home/builder/temporal/temporal/fx.go:1029): failed to build log.Logger: received non-nil error from function "<http://go.temporal.io/server/temporal|go.temporal.io/server/temporal>".ServerOptionsProvider (/home/builder/temporal/temporal/fx.go:180): sql schema version compatibility check failed: pq: SSL is not enabled on the server.```


<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1727247328039419) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["airbyte-platform", "helm-chart", "upgrade", "ssl-off", "temporal"]
</sub>

Hello Ravi, are you trying to use an external database to connect to temporal or it is a default values.yaml? If the first option, can you share more context of the database?

<@U01MMSDJGC9> Yes , I am using external database postgres deployed on Kubernetes via Helm chart

how did you manage it <@U077J3V8SPQ> (before 1.0)?

I have same issue with external Cloud SQL DB

I enabled ssl in postgres & it worked try for 0.524.0 version

v0.63.20 in docker-compose before migrating (but displayed as v0.63.13 in Airbyte UI)

hum ok as simple as it

I used helm file for installation

could you provide it ?

I would like to avoid configuring SSL :confused:

Nope that cant be avoided

does it mean Cloud SQL Proxy is useless ?

(we used to connect via this method before)

I am using postgres as external database which is deployed on Kubernetes via Helm chart & in that I have enabled SSL & it worked

I am not using AWS secret Manager then also got this error

hello <@U077J3V8SPQ>, did you finally succeeded ?

<@U05FB419LMR> Yes I succeed

I have one more issue while upgrading airbyte to 1.0.0

Error: INSTALLATION FAILED: YAML parse error on airbyte/charts/server/templates/deployment.yaml: error converting YAML to JSON: yaml: line 246: could not find expected ':'