dennismdejong opened a new pull request, #11697:
URL: https://github.com/apache/gravitino/pull/11697
### What changes were proposed in this pull request?
Make the Kubernetes secret name used by the `init-postgresql` init container
configurable via a new `postgresql.auth.existingSecretName` values field,
falling back to the Bitnami default `{{ .Release.Name }}-postgresql` when not
set.
### Why are the changes needed?
The Helm chart's `init-postgresql` init container hardcodes the secret name
as `{{ .Release.Name }}-postgresql`, which assumes the Bitnami PostgreSQL
subchart is always used. This breaks compatibility with external PostgreSQL
providers (CloudNativePG, CrunchyData, AWS RDS) where the secret name is
user-defined.
Fix: https://github.com/apache/gravitino/issues/11696
### Does this PR introduce any user-facing change?
Yes, adds `postgresql.auth.existingSecretName` (default: `""`) to
`values.yaml`.
### How was this patch tested?
- Existing helm unit tests pass (31 tests, 5 suites)
- New test case: default behavior produces `gravitino-postgresql`
- New test case: `existingSecretName=gravitino-cnpg-secret` produces that
name
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
