we’re up and running boiiii :rolling_on_the_floor_laughing:
<@U06JZBD5QER> saw that in another thread, ouch. We’re using standard auth with Cloud SQL right now, but likely moving toward IAM-based auth. so I’ll at least benefit from your pain :rolling_on_the_floor_laughing:
Let’s find out if not being able to add ?sslmode=require to the JDBC url is going to be a problem for me…
<@U056PF8U881> maybe this?
global.database.jdbcUrl
externalDatabase is completely unreferenced, but that is what I was using before. There doesn’t appear to be an eqivalent in global.database
This is where the chart builds the JDBC url now:
https://github.com/airbytehq/airbyte-platform/blob/175f77d6d570ed3f2c4df1fbcb67a23016c1cb4c/charts/airbyte/templates/_database.tpl#L165
oh boy
maybe try to append it to dbName
airbyte-database?sslmode=require
It might work without me adding that. The temporal chart now adds the SSL env vars automatically if you are using an external DB. Maybe the airbyte components will have a similar behaviour. I’ll report back when I’ve deployed the update. Jumping from 0.67.17 to 0.399.0 chart versions 
may the odds be ever in your favor
exactly what I did yesterday (except went to 0.390.0)
good luck 
be really mindful of those:
global:
storage:
type: gcs
storageSecretName: airbyte-gcs-log-creds
bucket:
log: splitc-production-airbyte
state: splitc-production-airbyte
workloadOutput: splitc-production-airbyte
activityPayload: splitc-production-airbyte
gcs:
authenticationType: credentials
and you still need to disable the internal postgres portion of the chart (for some reason)
yeah, thankfully that value hasn’t changed
everything seems to be working