Backup and recovery region in values.yaml not being used as expected#758
Open
ChrisTomAlxHitachi wants to merge 4 commits intocloudnative-pg:mainfrom
Open
Backup and recovery region in values.yaml not being used as expected#758ChrisTomAlxHitachi wants to merge 4 commits intocloudnative-pg:mainfrom
ChrisTomAlxHitachi wants to merge 4 commits intocloudnative-pg:mainfrom
Conversation
Signed-off-by: ChrisTomAlxHitachi <[email protected]>
Signed-off-by: ChrisTomAlxHitachi <[email protected]>
dosubot
bot
added
size:XS
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
1 participant
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.
In my testing I noticed the
regionvalue inValues.yamlseen in the following places are defaulting tous-east-1backups.s3.regionrecovery.s3.regionWhen testing in region
us-east-1I didn't face issues with either backup or recovery but when testing with regionbostonI noticed backups failing.On postgres I saw errors like
On my custom s3 I saw errors like