Postgres Operator Upgrade updates #1051
Merged
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
An updated procedure for upgrading the Postgres Operator from version 4.0.1 to 4.1 is required to account for recent configuration updates and environmental changes. These changes left certain Operator features nonfunctional. The new upgrade procedure is designed to ensure all applicable changes are accounted for in the most convenient way possible.
outlining the process to recreate the 4.0.1 clusters in the new 4.1.0 environment. Also added a reference to the pgo scaledown command's help for use when needing to scale down the existing PGO 4.0.1 pgclusters.
installation method for their Operator installation. Procedure is designed to be inclusive. Other updates reflect renaming of the existing procedure to specify it is for Bash installations, and an update to relevant links.
andrewlecuyer
approved these changes
Oct 15, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Checklist:
Type of Changes:
What is the current behavior? (link to any open issues here)
An updated procedure for upgrading the Postgres Operator from
version 4.0.1 to 4.1 is required to account for recent configuration
updates and environmental changes. These changes left certain
Operator features nonfunctional.
What is the new behavior (if this is a feature change)?
The new upgrade procedure is designed to ensure all applicable changes
are accounted for in the most convenient way possible.
Other information:
[ch5533]