You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Postgres password is regenerated on every chart apply, breaking existing installs #12229
On a helm upgrade (or any re-apply) this produces a new password, while the PostgreSQL data directory and its per-RP users were created with the previous password. The result is authentication failures against an already-initialized database — the RPs can no longer connect.
This is pre-existing behavior (not introduced by PR #12214), but PR #12214 makes the database path real/usable, so it now matters.
Acceptance criteria
The PostgreSQL password is stable across chart re-applies for an existing install.
A fresh install still generates a strong random password.
Additional context
The standard Helm pattern is lookup the existing Secret and reuse its password if present, otherwise generate a new one.
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Activity
radius-triage commentedon Jun 24, 2026
👋 @sylvainsf Thanks for filing this bug report.
A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.
For more information on our triage process please visit our triage overview
radius-triage commentedon Jun 29, 2026
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
nicolejms commentedon Jun 29, 2026
doesn't break current functionality. Expect users using postgres to use their helm chart and manage its lifecycle