<@U04S8PLJWMT> How can I use an external database ...
# replication-ask-ai
g
@kapa.ai How can I use an external database with tls disabled via Airbyte's helm chart 2.0.19 values?
k
The knowledge sources don't contain specific information about disabling TLS for an external database connection in Helm chart 2.0.19. However, they do cover the general external database configuration for Helm chart V2, which applies to recent versions. External Database Configuration (Helm Chart V2) Here's how to configure an external database in your `values.yaml`: Step 1: Create a Kubernetes Secret with your DB credentials
Copy code
apiVersion: v1
kind: Secret
metadata:
  name: airbyte-config-secrets
type: Opaque
stringData:
  database-user: your_user
  database-password: your_password
Step 2: Update
values.yaml
to disable the internal Postgres and point to your external DB
Copy code
postgresql:
  enabled: false

global:
  database:
    type: external

    # Secret name where database credentials are stored
    secretName: "airbyte-config-secrets"

    # The database host
    host: ""

    # The database port
    port: ""

    # The database name (key changed from "database" in V1 to "name" in V2)
    name: ""

    # The key within secretName where database user is stored
    userSecretKey: "database-user"

    # The key within secretName where password is stored
    passwordSecretKey: "database-password"
[External Database; Helm V2 upgrade] > Note on TLS: The knowledge sources do not explicitly mention how to disable TLS for the external database connection in the Helm chart V2
values.yaml
. The older forum posts mention that a
jdbcUrl
field (available in older Helm chart V1 configurations) could be used to pass additional JDBC driver arguments (e.g., for SSL handling), but this option is not documented in the V2 configuration. You may want to check the Airbyte documentation or open a GitHub issue for guidance specific to TLS settings in Helm chart V2. 👍 0 button 👎 0 button â„šī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
g
@kapa.ai The temporal pod is reporting this error: pq: SSL is not enabled on the server pq: SSL is not enabled on the server ; any thoughts?
k
This is a known issue when using an external PostgreSQL database that does not have SSL enabled, but the Temporal service is trying to connect with SSL. Based on the knowledge sources, there are a couple of relevant data points: 1. A similar issue was reported with Azure PostgreSQL, where the resolution was that "Azure PostgreSQL require a SSL certificate that wasn't available for temporal deployment, now that we have configured it, it works." [Temporal Azure Postgres] — meaning the fix there was to enable SSL on the DB side. 2. A Neon DB issue showed that the
airbyte-temporal
pod enters a crash loop when the external DB connection isn't configured correctly, preventing other services from starting. [Neon DB issue] In your case, the error
pq: SSL is not enabled on the server
means the Temporal service is attempting an SSL connection, but your PostgreSQL server doesn't have SSL enabled. You have two options: Option 1: Enable SSL on your PostgreSQL server (recommended) Enable SSL on your external Postgres instance. This is the recommended approach for production deployments. Option 2: Append
sslmode=disable
to the database name field
A workaround seen in community reports is to append the SSL mode parameter directly to the database name in `values.yaml`:
Copy code
postgresql:
  enabled: false

global:
  database:
    type: external
    secretName: "airbyte-config-secrets"
    host: "your-db-host"
    port: "5432"
    name: "your_db_name?sslmode=disable"  # append sslmode here
    userSecretKey: "database-user"
    passwordSecretKey: "database-password"
> Important caveat: The knowledge sources do not explicitly document
?sslmode=disable
as a supported parameter in Helm chart V2's
values.yaml
. This approach was observed in a community issue [Neon DB issue] where
?sslmode=require
was appended to the database name field. Whether
sslmode=disable
works the same way for Temporal's connection is not explicitly confirmed in the available knowledge sources. I'd recommend checking the Airbyte GitHub issues or opening a new issue for a definitive answer on disabling SSL for Temporal in Helm chart V2. 👍 0 button 👎 0 button â„šī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.