Skip to content

Postgres password is regenerated on every chart apply, breaking existing installs #12229

Open

Description

@sylvainsf

Overview

The database secret template generates the PostgreSQL password with randAlphaNum 16 on every chart apply:

# deploy/Chart/templates/database/configmaps.yaml
POSTGRES_PASSWORD: "{{ randAlphaNum 16 }}"

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

Activity

  1. added
    bugSomething is broken or not working as expected
    on Jun 24, 2026
  2. radius-triage commented on Jun 24, 2026

    @radius-triage

    👋 @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

  3. radius-triage commented on Jun 29, 2026

    @radius-triage

    👍 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

  4. nicolejms commented on Jun 29, 2026

    @nicolejms
    Contributor

    doesn't break current functionality. Expect users using postgres to use their helm chart and manage its lifecycle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or not working as expectedtriagedThis issue has been reviewed and triaged

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions