Hi @kapa.ai I upgraded to V1 chart - 1.8.5 My temporal was 1.23.0 now I swtiched to 1.27.2 After deployment, airbyte-server throws an error Server pod error: WARN i.g.o.k.KLogger$DefaultImpls(warn):695 - Ignoring exception while trying to request Temporal namespace: ││ airbyte-server-container io.grpc.StatusRuntimeException: UNAVAILABLE: io exception ││ airbyte-server-container at io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:351) ││ airbyte-server-container at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:332) ││ airbyte-server-container at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:174) ││ airbyte-server-container at io.temporal.api.workflowservice.v1.WorkflowServiceGrpc$WorkflowServiceBlockingStub.getSystemInfo(WorkflowServiceGrpc.java:6065) ││ airbyte-server-container at io.temporal.serviceclient.SystemInfoInterceptor.getServerCapabilitiesOrThrow(SystemInfoInterceptor.java:132) ││ airbyte-server-container at io.temporal.serviceclient.SystemInfoInterceptor$1.start(SystemInfoInterceptor.java:86) ││ airbyte-server-container at io.grpc.stub.ClientCalls.startCall(ClientCalls.java:418) ││ airbyte-server-container at io.grpc.stub.ClientCalls.asyncUnaryRequestCall(ClientCalls.java:394) ││ airbyte-server-container at io.grpc.stub.ClientCalls.futureUnaryCall(ClientCalls.java:307) ││ airbyte-server-container at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:163) ││ airbyte-server-container at io.temporal.api.workflowservice.v1.WorkflowServiceGrpc$WorkflowServiceBlockingStub.describeNamespace(WorkflowServiceGrpc.java:5531) ││ airbyte-server-container at io.airbyte.commons.temporal.TemporalUtils.getNamespaceInfo(TemporalUtils.kt:211) ││ airbyte-server-container at io.airbyte.commons.temporal.TemporalUtils.getTemporalClientWhenConnected(TemporalUtils.kt:189) ││ airbyte-server-container at io.airbyte.commons.temporal.TemporalUtils.createTemporalService(TemporalUtils.kt:78) ││ airbyte-server-container at io.airbyte.commons.temporal.TemporalUtils.createTemporalService(TemporalUtils.kt:104) ││ airbyte-server-container at io.airbyte.commons.temporal.config.TemporalBeanFactory.temporalService(TemporalBeanFactory.kt:33) ││ airbyte-server-container at io.airbyte.commons.temporal.config.$TemporalBeanFactory$TemporalService0$Definition.instantiate(Unknown Source) ││ airbyte-server-container at io.micronaut.context.DefaultBeanContext.resolveByBeanFactory(DefaultBeanContext.java:2337) And this is the error from airbyte-temporal pod. TEMPORAL_ADDRESS is not set, setting it to 192.168.13.218:7233 ││ PostgreSQL started. ││ Setup PostgreSQL schema. ││ 2026-03-04T162750.684Z ERROR sql handle: unable to refresh database connection pool {"error": "unable to connect to DB, tried default DB names: postgres,defaultdb, errors: [pq: SSL is not enabled on the server pq: SSL is not enabled on the server]", "logging-call-at": "/home/runner/work/docker-builds/ ││ 2026-03-04T162750.684Z 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-04T162750.684Z ERROR Unable to create SQL database. {"error": "no usable database connection found", "logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/sql/handler.go:93"} I used to have this error before so i had to use temporal tool to create the databases and initialze default namespace for 1.23.0 Since i changed to 1.27.2 should i redo the whole proccess again? Can you help me here

The error in your

airbyte-temporal

pod is the key issue here:

unable to connect to DB, tried default DB names: postgres,defaultdb, errors: [pq: SSL is not enabled on the server pq: SSL is not enabled on the server]

This indicates that Temporal 1.27.2 is attempting to connect to your PostgreSQL database using SSL, but SSL is not enabled on your database server. This is a connectivity issue between Temporal and your external PostgreSQL instance, not necessarily a schema/namespace issue. This is similar to a known pattern where Azure PostgreSQL (or other managed databases) require SSL certificates that aren't configured for the Temporal deployment. [Temporal Azure Postgres] Here's what you should check and do: 1. Resolve the SSL Issue First The

airbyte-server

error (

UNAVAILABLE: io exception

) is a downstream consequence of Temporal not starting properly. Fix the Temporal → PostgreSQL connection first. • If your PostgreSQL instance does not support SSL, you may need to configure Temporal to connect without SSL (e.g., by setting

POSTGRES_TLS_ENABLED=false

or similar env vars via

temporal.extraEnv

in your

values.yaml

). • If your PostgreSQL instance requires SSL, you need to provide the appropriate SSL certificates/configuration to the Temporal pod. You can pass extra environment variables to the Temporal pod using the

extraEnv

field in your Helm values: [Values.yaml reference]

temporal:
  extraEnv:
    - name: SQL_TLS_ENABLED
      value: "false"
    # or configure SSL cert paths if SSL is required

2. Regarding Re-running Schema Setup The knowledge sources do not explicitly confirm whether upgrading from Temporal 1.23.0 to 1.27.2 requires re-running the schema/namespace initialization. However, since Temporal cannot even connect to the database right now (due to the SSL error), the schema issue is secondary — you need to fix the SSL connectivity problem first. Once Temporal can connect to PostgreSQL successfully, if you still see schema-related errors, you may need to re-run the schema setup steps you performed previously for 1.23.0. Summary 1. Fix the SSL mismatch between Temporal 1.27.2 and your PostgreSQL instance (either disable SSL on the Temporal side or enable/configure it on the DB side). 2. Once Temporal starts successfully, check if the

airbyte-server

error resolves on its own. 3. If schema/namespace errors persist after connectivity is restored, you may need to re-initialize the schema and namespace. I'd recommend checking your PostgreSQL server's SSL configuration and aligning it with what Temporal 1.27.2 expects. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.