-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pb-3494: vendor latest kdmp repo from 1.2.4 branch #1274
Open
siva-portworx
wants to merge
18
commits into
master
Choose a base branch
from
pb-3494
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
* PB-3397: Add Logic to support namespace label selector in the application backup controller - These feature is supported with manual and schedule backups - Currently Namespaces come along the application backup spec consider to be backed up, Now these namespaces are selected using the namespace selectors provided as part of the same spec at execution time. - Filtered namespaces that to be backed up are also updated to the data-store object while reconciling.
Signed-off-by: Rohit-PX <[email protected]>
Signed-off-by: Kesavan Thiruvenkadasamy <[email protected]>
Signed-off-by: Kesavan Thiruvenkadasamy <[email protected]>
Signed-off-by: Kesavan Thiruvenkadasamy <[email protected]>
* Added test for Clone PVCs after DR on destination cluster * Added test for Clone PVCs after DR on dest cluster * modified test to chec pvc bound * modified test to check pvc bound * Addressed review comments * Added changes to use storageclassName instead of storage class in annotations for clone pvc test --------- Co-authored-by: root <[email protected]> Co-authored-by: GEET JAIN <[email protected]> Co-authored-by: geet <[email protected]> Co-authored-by: root <[email protected]> Co-authored-by: Rohit-PX <[email protected]>
Signed-off-by: Priyanshu Pandey <[email protected]>
siva-portworx
requested review from
lalat-das,
diptiranjanpx,
prashanthpx and
px-kesavan
February 8, 2023 08:21
Can one of the admins verify this patch? |
siva-portworx
force-pushed
the
pb-3494
branch
from
February 8, 2023 14:23
a77868b
to
4ecc201
Compare
lalat-das
approved these changes
Feb 8, 2023
siva-portworx
force-pushed
the
pb-3494
branch
2 times, most recently
from
February 8, 2023 18:13
7de03f9
to
cbd024e
Compare
siva-portworx
force-pushed
the
pb-3494
branch
from
February 9, 2023 03:27
cbd024e
to
b2b0d4a
Compare
siva-portworx
force-pushed
the
pb-3494
branch
from
February 9, 2023 04:38
b2b0d4a
to
a0df07a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
What this PR does / why we need it:
Does this PR change a user-facing CRD or CLI?:
no
Is a release note needed?:
Does this change need to be cherry-picked to a release branch?:
no