Postgres password readed from secret keys

[MarcinRybinski]

Hello Langfuse team,

Context

When deploying Langfuse with your Helm chart, I've encountered a small issue when providing postgres password from secretKey refs:

My configuration for postgres was:

postgresql:
  auth:
    username: postgres
    existingSecret: langfuse-postgresql-auth
    secretKeys:
      userPasswordKey: password

But the deployment was unsuccessfull. When I looked into definition of postgres StatefulSet, I've seen that:

- name: POSTGRES_PASSWORD
  valueFrom:
    secretKeyRef:
      key: postgres-password
      name: langfuse-postgresql-auth

The key was referencing to the postgres-password, but not to the password field.

I've looked into implementation of Postgresql Bitnami Helm Chart how they are creating POSTGRES_PASSWORD env variable and it seems like when the username for postgresql database is postgres, it is reaching out to the adminPasswordKey in secretKeys, but not to the userPasswordKey. If adminPasswordKey is missing in the configuration, it defaults to postgres-password key.
The solution to my problem was to change the userPasswordKey to adminPasswordKey:

postgresql:
  auth:
    username: postgres
    existingSecret: langfuse-postgresql-auth
    secretKeys:
      adminPasswordKey: password

And it worked.

Problem

I'm reaching out to you with this issue because:

1. Default username in values.yaml is postgres
2. You're referencing to the secretKeys: userPasswordKey in values.yaml which wont work because postgresql chart expect adminPasswordKey when the username is postgres

Proposed solution

I currently don't know which of the proposed solution would be the best, because I'm familiarized with the repo like you, but from my basic knowledge and understanding what's going on in your Helm chart, I see two options:

1. Document this in the Readme
2. Or change the way you set up DATABASE_PASSWORD

[dosubot]

Hello @MarcinRybinski! I'm here to help you with bugs, questions, and becoming a contributor. Let's squash those bugs together! 🤖

To address the issue with the Postgres password configuration in the Langfuse Helm chart, you should update the values.yaml file to use adminPasswordKey instead of userPasswordKey when the default username is postgres. This change aligns with the behavior of the Bitnami PostgreSQL chart, which defaults to using adminPasswordKey for the postgres user. Here's how you can modify your configuration:

postgresql:
  auth:
    username: postgres
    existingSecret: langfuse-postgresql-auth
    secretKeys:
      adminPasswordKey: password

This adjustment ensures that the correct key is referenced for the Postgres password, resolving the deployment issue you encountered ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[andresC98]

Hi, in our case, we do the postgres auth values.yaml as following and we encounter no problem (at helm chart version 1.0.0-rc10)

postgresql:
  auth:
    existingSecret: postgres-password-secret
    secretKeys:
      userPasswordKey: postgres-password

The postgres db initializes successfully and langfuse instance is able to do auth.

Check if the volume where postgres instance is attached to has not been reset as it is possible that if you change the password value, the old postgres conf file did not change and thus whenever the instance is restarted is not picking up the new password from the value and instead is picking up the old one, thus langfuse tries authenticating with the new one and fails.

That happened to us and we had to delete the old PV/PVC where postgres was attached and restart and it worked.