Closed MuhanedYahya closed 1 month ago
Thank you for opening this. @itay-grudev is currently working on our Charts to revamp them. I've flagged this to him to make sure it is tested
No worries, I'll include it in the test suite.
Will this fix be ready in 2 weeks?
Will this fix be ready in 2 weeks?
Yes, it should be. What is your use case/organization?
Hi @MuhanedYahya. We are moving to https://github.com/paradedb/charts, which is based on the official CloudNativePG Charts, with help from @itay-grudev.
This is supported in those charts. ParadeDB support will be released for it within the week
Nice to hear that. Honestly, I can’t share too much about the intended use, but you can check my profile to get a general sense of my background. https://www.linkedin.com/in/muhaned-yahya
Bug Description When appUserCredentials and superUserCredentials are provided via values.yaml, new secrets are created during deployment. If these secrets already exist, the deployment fails with an error. This issue prevents the deployment of Paradedb in environments where sealed-secrets are used, as it cannot handle pre-existing secrets.
Proposed Fix add option like (
existingSecret: SECRET_ NAME)
under both of the sections appUserCredentials and superUserCredentials without the need to enter other valuesAfter the correction I expect: