[bitnami/postgresql] Adapt to Helm v3 and change nomenclature #4385
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
…res-terminology-change
…nami-charts into postgresqlMajor
carrodher
reviewed
Nov 17, 2020
bitnami/postgresql/README.md
Outdated
| - https://helm.sh/docs/topics/v2_v3_migration/ | ||
| - https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/ | ||
|
|
||
| #### Breaking changes |
There was a problem hiding this comment.
Add here a paragraph about the breaking changes in this major, the ones related to the renaming
There was a problem hiding this comment.
That is explained above, deleting this empty section
|
I have just updated the bitnami images with the latest known immutable tags:
|
This was referenced Nov 18, 2020
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.
Description of the change
This PR adapts the bitnami/postgresql to the Helm v3 apiversion v2 and changes the nomclature for master and slave to primary and readReplica.
We are taking ownership of #4049
Benefits
Possible drawbacks
Applicable issues
Additional information
Checklist
Chart.yamlaccording to semver.[bitnami/chart])values-production.yamlapart fromvalues.yaml, ensure that you implement the changes in both files