Bug
The db-seed init container in the netbird-server pod fails to connect to PostgreSQL when the database password contains URL-special characters (@, %, !, etc.).
Root Cause
The seed.yaml template in the netbird-server configmap constructs a URL-style connection string:
postgres://postgres:{{ env.DB_PASSWORD }}@host:5432/?sslmode=disable
When DB_PASSWORD contains @, it is parsed as the userinfo/host delimiter, breaking the URI. % is interpreted as percent-encoding. The TCP connectivity check (db-wait) passes because it only tests the socket, not auth/parsing.
Suggested Fix
Either:
- URL-encode
{{ env.DB_PASSWORD }} before embedding it in the connection URI, or
- Switch
seed.yaml to a DSN-style connection string (host=... password=...) which does not require encoding.
Environment
- Chart:
netbird-0.2.1
- initium:
1.2.0
Bug
The
db-seedinit container in the netbird-server pod fails to connect to PostgreSQL when the database password contains URL-special characters (@,%,!, etc.).Root Cause
The
seed.yamltemplate in the netbird-server configmap constructs a URL-style connection string:When
DB_PASSWORDcontains@, it is parsed as the userinfo/host delimiter, breaking the URI.%is interpreted as percent-encoding. The TCP connectivity check (db-wait) passes because it only tests the socket, not auth/parsing.Suggested Fix
Either:
{{ env.DB_PASSWORD }}before embedding it in the connection URI, orseed.yamlto a DSN-style connection string (host=... password=...) which does not require encoding.Environment
netbird-0.2.11.2.0