pb-4669: Adding support for partial success backups#1579
Open
prashanthpx wants to merge 1 commit intopartial_success_pb_4585from
Open
pb-4669: Adding support for partial success backups#1579prashanthpx wants to merge 1 commit intopartial_success_pb_4585from
prashanthpx wants to merge 1 commit intopartial_success_pb_4585from
Conversation
Collaborator
|
Can one of the admins verify this patch? |
prashanthpx
requested review from
diptiranjanpx,
kgarg-px,
lalat-das,
px-kesavan,
siva-portworx and
vsundarraj-px
- A backup involving multiple PVC, if one of the PVC backup fails, backup will mark that PVC as Failed and proceed to next PVCs rather than failing the entire backup - For the failed PVC, corresponding resources are not backed up. - New status called PartialSuccess is introduced to signify the same
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.
What type of PR is this?
Improvement
What this PR does / why we need it:
Does this PR change a user-facing CRD or CLI?:
No
Is a release note needed?:
Yes
Does this change need to be cherry-picked to a release branch?:
Yes
Note
All test notes are captured in ticket PB-4669