Fix bitnami/postgresql subchart upgrade #29210
Closed
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
dnskr
force-pushed
the
complete_bitnami_postgresql_upgrade
branch
from
0a64f47 to
6aebcab
Compare
|
Needs tests fix as well. |
dnskr
force-pushed
the
complete_bitnami_postgresql_upgrade
branch
from
6aebcab to
ecc0c80
Compare
|
Closed in favor of pinning Postgres 11 version for the helm chart 1.8.0, see #29207. |
2 tasks
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.
The PR changes default
pgbouncer.auth_typevalue toscram-sha-256.It fixes the case when installing the chart with enabled
pgbouncer, i.e. the following deployment:The issue was introduced when bitnami/postgres subchart was upgraded to 12.1.9 version. Previous bitnami/postgres subchart deploys Postgres 11 with default auth type md5, current version deploys Postgres 15 with default auth type scram-sha-256.
related: #29071 and #29207