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

Cloudnative-PG DB Secret Integration #12

Open
tctlrd opened this issue Aug 9, 2024 · 5 comments
Open

Cloudnative-PG DB Secret Integration #12

tctlrd opened this issue Aug 9, 2024 · 5 comments
Assignees
Labels
enhancement New feature or request stale

Comments

@tctlrd
Copy link
Contributor

tctlrd commented Aug 9, 2024

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...

@vindelicus
Copy link
Contributor

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! 👍🏼

@vindelicus vindelicus self-assigned this Aug 9, 2024
@vindelicus vindelicus added the enhancement New feature or request label Aug 9, 2024
@cfarence
Copy link

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
Copy link
Contributor Author

tctlrd commented Aug 13, 2024

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

Copy link

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 github-actions bot added the stale label Sep 12, 2024
@vindelicus vindelicus removed the stale label Nov 7, 2024
Copy link

github-actions bot commented Dec 8, 2024

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 github-actions bot added the stale label Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

3 participants