Avoid rotating pods for PGVERSION change outside of maintenance window#3065
Merged
Avoid rotating pods for PGVERSION change outside of maintenance window#3065
Conversation
hughcapet
requested review from
FxKu,
Jan-M,
idanovinda,
jopadi and
sdudoladov
as code owners
Member
|
👍 |
1 similar comment
Member
Author
|
👍 |
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
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.
Do reset of
PGVERSIONduring Sync() before the setSpec() call, like in Update() to avoid disruptions caused byPGVERSIONenvironment variable mismatch outside of the maintenance windows