fmjstudios / helm

🪖 A collection of MIT-licensed Helm Charts
MIT License
13 stars 13 forks source link

Cloudnative-PG DB Secret Integration #12

Closed tctlrd closed 5 months ago

tctlrd commented 11 months ago

Name and Version

vaultwarden, linkwarden, cachet, activepieces, paperless-ngx

What is the problem this feature will solve?

Folks using the CNPG operator already have a secret with the database credentials. This feature will allow the chart to use that secret to connect the app to the database. Charts in the fmjstudios repo using PostgreSQL: vaultwarden, linkwarden, cachet, activepieces, paperless-ngx

What is the feature you are proposing to solve the problem?

Include an optional value for charts using PostgreSQL that applies the database secret created by the official CNPG (Cloudnative-PG) operator, in order to connect the app to the database.

What alternatives have you considered?

Manually entering credentials for databases...

mvprowess commented 11 months ago

Hey @tctlrd, very valid point! I use the Operator myself but haven't actually gotten to properly deploy my charts since I'm reworking the cluster at the moment. I will take a look at this and the required changes over the next few days and report back! 👍🏼

cfarence commented 11 months ago

paperless-ngx also supports mariadb and I already use that operator with backups, would be nice to be able to simply use that. Currently it appears the db vendor is hard coded in the configmap in the chart.

tctlrd commented 11 months ago

@cfarence Integrating with both the mariadb & postgresql operator secrets in the same PR would make sense. To avoid complexity I am trying run as much as possible on postgresql: https://www.amazingcto.com/postgres-for-everything/

github-actions[bot] commented 10 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 7 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 5 months ago

false