-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Update main #214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Update main #214
Conversation
This file contains hidden or 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
Major PG Upgrades is now integrated into a single postgres-operator binary. Deployment of a separate upgrade binary is no longer needed. Issue: [sc-16349] Co-authored-by: Drew Sessler <drew.sessler@gmail.com>
…runchyData#185) * Adding capability to stream off of a primary due to feature addition in PGOv5.3, removing requirement to specify a repo when standby is enabled. * Removing outdated comment about required standby values and specifying more realistic values for host and port. * Changing port value to an integer Issue: [sc-17928]
keyType was missing from the list of s3 config fields.
Now that we've had 2 patch releases of Postgres 15 we are dropping postgres 13. Issue [sc-17907]
Issue [sc-17991]
Applies fixes contributed by dajeffers in PR 3307 for CrunchyData/postgres-operator. Issue: [sc-20286]
Users can now provide custom pod labels through the values.yaml file. Any labels that overlap with Crunchy labels will lead to duplicate labels on the resource and errors returned from the Kube API when creating the templated resource.
Allow user to provide pod labels via values.yaml
[sc-19940]
Co-authored-by: Benjamin Blattberg <benjamin.blattberg@gmail.com>
Co-authored-by: Benjamin Blattberg <benjamin.blattberg@gmail.com>
Co-authored-by: Benjamin Blattberg <benjamin.blattberg@gmail.com>
[sc-18203]
* Add keyType to postgres s3 helm template keyType was missing from the list of s3 config fields.
releases of Postgres 15 we are dropping postgres 13. Issue [sc-17907]
Issue: [sc-17991]
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.
No description provided.