fix: updated database recovery instructions #125
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
|
Could add a segment on how to create manual backups? Those now need the method: plugin and plugin defenition. |
Yes, this was not part of the change but we should add it. The simplest method is installing the CNPG plugin for kubectl and creating the backup from there, e.g.: kubectl cnpg backup -n gitea gitea-db -m plugin --plugin-name barman-cloud.cloudnative-pg.io |
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.
With recent changes to CloudnativePG backup and archiving, as also implemented in Core, the instructions for recovery have been updated in this PR.
These should be published not before the release of the matching Core changes, since some references to new objects will otherwise not exist in the cluster. However, the previous approach for recovery should still work.Update: The change is released, and these instructions can be published. The previous approach should still work however, as CloudnativePG in its current version supports both.