[HELM] - Add guide how to PgBouncer with Kubernetes Secret #42460
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andormarkus
requested review from
dstandish and
jedcunningham
as code owners
potiuk
approved these changes
Oct 2, 2024
|
Nice! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi All,
Do company polices we can not store secrets in the
values.yamland we need to use Kubernetes Secrets. These requirements made the PgBouncer implementation ver challenging because the the helm chart is able to handle external database until it is fully defined in thevalues.yamlhowever if it is defined the Kubernetes Secret than the PgBouncer does not pick up these changes and wan't to connect to the local Postgres DB which is not deployed because external database was used.To be able to PgBouncer work we need to create two Kubernetes Secrets manually and reference is in the chart.
I have extended the helm documentation if someone else in the future can have countless hours on deployment