-
Notifications
You must be signed in to change notification settings - Fork 12
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
Comments
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! 👍🏼 |
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. |
@cfarence |
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. |
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. |
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...
The text was updated successfully, but these errors were encountered: