[helm] `DATABASE_URL` ignored by Temporal pods
What method are you using to run Airbyte?
Kubernetes
Platform Version or Helm Chart Version
0.50.34
What step the error happened?
Other
Revelant information
We have the externalDatabase.jdbcUrl parameter used to enable SSL when Airbyte connects to its database.
(cf. https://github.com/airbytehq/airbyte/issues/17995)
The main database is therefore covered. This however doesn't work for temporal components and their dbs (temporal and temporal-visibility).
I tried to inject the DATABASE_URL into the temporal container and it is present there as an env variable, but it is very much ignored when connection happens. There's also no variables I found in the doc that I could pass connection params to and have them respected.
I'm logging it as an issue, but if there's another way to enforce it, please let me know 🙏
Cf. this comment too
Relevant log output
No response
any update to related this issue? because i have also the similar issue while passing the jdbcUrl on helm charts it seems failing:
2024-02-06T06:54:26.452Z [31mERROR[0m Unable to create SQL database. {"error": "unable to connect to DB, tried default DB names: postgres,defaultdb, errors: [pq: connection is insecure (try using `sslmode=require`) pq: connection is insecure (try using `sslmode=require`)]
@monik-a @mrfzy00 Hello guys. Have you ever tried below?
temporal:
extraEnv:
- name: SQL_TLS
value: "true"
- name: SQL_TLS_DISABLE_HOST_VERIFICATION
value: "true"
- name: SQL_TLS_ENABLED
value: "true"
- name: SQL_HOST_VERIFICATION
value: "false"
I had the same temporal SSL encryption problem, which is resolved by that configuration. (Refer: https://github.com/airbytehq/airbyte/issues/11157#issuecomment-1927515718)
@minyukim thanks, I already resolved that with enabling SSL TLS via the db instances and it worked. cheers!
At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.
Please keep it open
At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.
Please keep it open
At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.
Please keep it open