fix: use bitnamilegacy repo for postgres and pgbouncer #420
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.
Thanks for submitting a PR! Please check the boxes below:
Changes
This implements a temporary fix due to the changes introduced by this [1]. I also looked into other ways to handle this, e.g., using a different image with the same Bitnami chart or moving to a different chart. All of those options also feel like temporary fixes, so we might as well move to bitnamilegacy for now. The permanent fix would be to move away from the Bitnami chart entirely, use the Docker images directly, and handle the minimal setup that the Bitnami charts currently provide.
[1]: #386
How did you test this code?
Installed this chart on minikube