bug: fail to connect to Postgres 18

[tampler]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe the bug

Hello

Kratos doesn't connect to PostgreSQL 18, running from Kubernetes. Seems like it can't parse DSN

Error is below:

kratos-f4c5f64b9-978jf kratos time=2025-11-22T19:00:35Z level=debug msg=No SQL connection options have been defined, falling back to default connection options. audience=application service_name=Ory Kratos service_version=v25.4.0 sql_max_connection_lifetime=0s sql_max_connections=8 sql_max_idle_connection_time=0s sql_max_idle_connections=4     kratos-f4c5f64b9-978jf kratos time=2025-11-22T19:00:35Z level=debug msg=Connecting to SQL Database audience=application connMaxLifetime=0s idlePool=4 pool=8 service_name=Ory Kratos service_version=v25.4.0                                                                                                                                              kratos-f4c5f64b9-978jf kratos time=2025-11-22T19:00:35Z level=warning msg=Unable to determine network, retrying. audience=application error=map[debug: message:Unable to locate the table reason: stack_trace:                                                                                                                                            kratos-f4c5f64b9-978jf kratos github.com/ory/x/sqlcon.handlePostgres                         

My setup works

• with PostgreSQL 17
• with hydra chart version v0.60.0 with image v25.4.0

That's why I think it's an issue with Kratos, which needs to add PostgreSQL 18 support.

PS: Envs are imported correctly and specified as a secret in Kubernetes (see below)

Reproducing the bug

1. helm install kratos ory/kratos -f kratos.yml // fails
2. helm install kratos ory/kratos --version=0.58.0 -f kratos.yml // fails with older version too

Relevant log output

Relevant configuration

Version

v25.4.0

On which operating system are you observing this issue?

None

In which environment are you deploying?

None

Additional Context

K8s: v1.33.5
chart: v0.60.0
kratos: v25.4.0

[tampler]

I found that this error occurs due to invalid or absent db migrations.

kratos-courier seems to have finished migrations, but they won't work 🙄

Workaround

• create db
• run cli migrations manually: kratos migrate sql up -e
• deploy kratos with helm

Running SQL migrations manually before deploying a kratos solves the issue

[tampler]

I was able to resolve this issue. My problem was in a helm chart configuration, which changed in the recent chart.
To avoid the db init issues, make sure to enable automigration in your helm chart:

kratos:
  version: v25.4.0
  dev: false

  automigration:       < --- add this
    enabled: true

Sincerely,
Boris