Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

externalDB doesn't allow different components to be read from values #487

Open
jonathanmccracken opened this issue Jan 19, 2025 · 1 comment

Comments

@jonathanmccracken
Copy link

Ideally we can set each component of the connection string allowing to read these from configmaps/secrets in k8s.

eg
externalDB: dbUsername: "foo" dbPassword: "bar" # or fromExternalSecret ....
Alternatively these could also reference an external secret like many other helm charts -
https://github.com/immich-app/immich-charts/blob/4b3e1d4d0b15a30db33bc76fb847b89d0f8bd6f0/charts/immich/values.yaml#L12

Relevant lines:
https://github.com/mattermost/mattermost-helm/blob/0ce91320ff8ec9f79ae07bc64ea700553cc811f2/charts/mattermost-team-edition/values.yaml#L94C1-L96C30

@jonathanmccracken
Copy link
Author

jonathanmccracken commented Jan 24, 2025

Tried to close this using cloudnative-pg's created secrets

externalDB:
      enabled: true
      externalDriverType: postgres
      externalConnectionString: 
        valuesFrom:
          secretKeyRef:
            name: mattermost-pgsql-app
            key: uri

Problem remains open as the part of the uri is embedded in matter most's configmap - so the component "postgres://" shows up twice.

Ideally some way to configure each component of the database would solve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant