https://linen.dev logo
Join Slack
Powered by
hi, i am deploying airbyte via helm in my k8s clus...
# replication-ask-ai
m
hi, i am deploying airbyte via helm in my k8s cluster. i am facing issues with temporal pod setup when trying to use my own database: 
TEMPORAL_ADDRESS is not set, setting it to 0.0.0.0:7233
PostgreSQL started.
Setup PostgreSQL schema.
2026-03-30T08:19:27.337Z	ERROR	sql handle: unable to refresh database connection pool	{"error": "pq: no pg_hba.conf entry for host \"10.156.183.91\", user \"tian_temporal\", database \"temporal\", no encryption", "logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/common/persistence/sql/sqlplugin/db_handle.go:128"}
2026-03-30T08:19:27.337Z	INFO	Starting schema setup	{"config": {"SchemaFilePath":"","SchemaName":"","InitialVersion":"0.0","Overwrite":false,"DisableVersioning":false}, "logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/setuptask.go:64"}
2026-03-30T08:19:27.337Z	DEBUG	Setting up version tables	{"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/setuptask.go:74"}
2026-03-30T08:19:27.337Z	WARN	sql handle: did not refresh database connection pool because the last refresh was too close	{"min_refresh_interval_seconds": 1, "logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/common/persistence/sql/sqlplugin/db_handle.go:118"}
2026-03-30T08:19:27.337Z	ERROR	Unable to setup SQL schema.	{"error": "no usable database connection found", "logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/sql/handler.go:56"}
my config in values.yaml:
Copy code
temporal:
  resources: *mainResources
  secretName: airbyte-secrets
  database:
    host: hosturl
    port: 5432
    name: tian_temporal
    userSecretKey: temporal-db-user
    passwordSecretKey: temporal-db-password
can somebody support with that issue? @kapa.ai
k
The error message is very telling:
Copy code
pq: no pg_hba.conf entry for host "10.156.183.91", user "tian_temporal", database "temporal", no encryption
This means your PostgreSQL instance is rejecting the connection from the Temporal pod because: 1. The host IP (
10.156.183.91
) is not allowed in the 
pg_hba.conf
file of your PostgreSQL server, and/or 2. No encryption (SSL) is being used, and your PostgreSQL server requires it. This is a PostgreSQL access control issue, not an Airbyte configuration issue per se. Here are the steps to resolve it: 1. Allow the Kubernetes pod network in pg_hba.conf You need to add an entry in your PostgreSQL 
pg_hba.conf
to allow connections from the Kubernetes pod CIDR. For example:
Copy code
host    temporal    tian_temporal    10.156.0.0/16    md5
Adjust the CIDR to match your Kubernetes pod network range. 2. SSL/Encryption requirement If your PostgreSQL instance requires SSL, you may need to configure the Temporal connection to use SSL. A similar issue was reported with Azure PostgreSQL, where the fix was to configure an SSL certificate for the Temporal deployment. [Azure Postgres SSL fix] 3. Ensure the temporal and temporal_visibility databases exist Even after fixing the connection issue, make sure the required databases are pre-created, as Temporal needs them and the database user may not have 
CREATE DATABASE
permissions:
Copy code
CREATE DATABASE temporal WITH OWNER = tian_temporal;
CREATE DATABASE temporal_visibility WITH OWNER = tian_temporal;
GRANT ALL PRIVILEGES ON DATABASE temporal TO tian_temporal;
GRANT ALL PRIVILEGES ON DATABASE temporal_visibility TO tian_temporal;
[External DB setup] [RDS setup issue] Summary The root cause is that your PostgreSQL server's 
pg_hba.conf
is not configured to accept connections from the Kubernetes pod IP range, and/or SSL is required but not configured. Fix the 
pg_hba.conf
(or firewall/security group rules if using a managed DB like RDS/Cloud SQL) to allow the pod network, and ensure SSL settings match between the client and server. 👍 0 button 👎 0 button ℹī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
m
but why is the error log:
Copy code
sql handle: unable to refresh database connection pool	{"error": "pq: no pg_hba.conf entry for host \"10.156.183.91\", user \"tian_temporal\", database \"temporal\", no encryption"
it tries to connect to DB "temporal" but my config says db name is"tian_temporal":
Copy code
temporal:
  resources: *mainResources
  secretName: airbyte-secrets
  extraEnv:
    - name: SKIP_DB_CREATE
      value: "true"
  database:
    host: hostname
    port: 5432
    name: tian_temporal
    userSecretKey: temporal-db-user
    passwordSecretKey: temporal-db-password
It explicitly says that db name is "tian_temporal" @kapa.ai
k
This is a great observation. The knowledge sources do not contain detailed documentation about how Airbyte's Helm chart maps the 
temporal.database.name
value to the actual database name used by the Temporal service internally. However, based on the error log, Temporal is attempting to connect to a database literally named 
temporal
 (not 
tian_temporal
), which suggests that the 
temporal.database.name
field in your 
values.yaml
may be controlling something different (e.g., the Airbyte application database for Temporal's config), while the Temporal service itself always tries to create/connect to databases named 
temporal
and 
temporal_visibility
 by default. This behavior is consistent with what's documented in the knowledge sources — for example, one forum post notes: > "Temporal targets separate databases named 
temporal
and `temporal_visibility`" [Neon DB issue] And another user confirmed: > "Temporal auto-setup requires... databases named 
temporal
and `temporal_visibility`" [Temporal DB permissions] So it appears that regardless of what you set in 
temporal.database.name
, the Temporal service internally hardcodes the database names 
temporal
and 
temporal_visibility
. Your 
tian_temporal
setting may refer to the user or a different config field, not the Temporal schema database name. What you likely need to do 1. Create databases named exactly 
temporal
and 
temporal_visibility
 on your PostgreSQL instance and grant your 
tian_temporal
user access to them. 2. Allow the pod IP (
10.156.183.91
) in 
pg_hba.conf
 for those databases and that user. The knowledge sources do not provide further detail on whether the 
temporal.database.name
field can override the hardcoded 
temporal
database name in the Temporal service. I'd recommend checking the Airbyte Helm chart's 
values.yaml
schema or opening a GitHub issue for clarification on what exactly 
temporal.database.name
controls. 👍 0 button 👎 0 button ℹī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
m
how can i configure the sslMode for db connection from temporal? @kapa.ai
k
The knowledge sources do not contain specific documentation about how to configure SSL mode for the Temporal database connection in Airbyte's Helm chart. The 
temporal.database
section's SSL configuration options are not documented in the provided sources. What the knowledge sources do confirm is that SSL is a known requirement for some managed PostgreSQL providers (like Azure PostgreSQL), and that configuring the SSL certificate for the Temporal deployment resolved the connection issue in at least one case: [Azure Postgres SSL fix] For the main Airbyte application database (not Temporal specifically), there is no SSL configuration option exposed in the 
global.database
section of 
values.yaml
based on the available docs. [External DB setup] One workaround that has been mentioned in the context of the Neon DB issue is appending 
?sslmode=require
directly to the database name string in the config (e.g., 
database: "neondb?sslmode=require"
), though this approach was noted in a bug report and its effectiveness for Temporal specifically was not confirmed. [Neon DB issue] I'd recommend: 1. Checking the Airbyte Helm chart's full 
values.yaml
schema on GitHub for any 
sslMode
or 
ssl
fields under the 
temporal.database
section. 2. Opening a GitHub issue or checking the Airbyte Slack community for guidance specific to your setup, as this level of detail is not covered in the available knowledge sources. 👍 0 button 👎 0 button ℹī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
2 Views
Open in Slack
PreviousNext
Powered by