Open
Conversation
Signed-off-by: Ram <rsuradkar@purestorage.com>
…ation, delete error and multitenancy. Signed-off-by: Priyanshu Pandey <ppandey@purestorage.com>
…tal error. Signed-off-by: Priyanshu Pandey <ppandey@purestorage.com>
Signed-off-by: Priyanshu Pandey <ppandey@purestorage.com>
Signed-off-by: Ram <rsuradkar@purestorage.com>
Signed-off-by: Ram <rsuradkar@purestorage.com>
Signed-off-by: Ram <rsuradkar@purestorage.com>
- validate specs for resource transformation cr - apply patch on unstruct k8s objects - run patched resources on dry run namespace with DryRun option set to all Signed-off-by: Ram <rsuradkar@purestorage.com>
…-dr setups - query cluster pair token using px endpoint + port - query port by looking at px-api service rest port Signed-off-by: Ram <rsuradkar@purestorage.com>
- accept resource transformation in migration spec - update resource as per transformation rule Signed-off-by: Ram <rsuradkar@purestorage.com>
- allow dry run for keypair and slice value type Signed-off-by: Ram <rsuradkar@purestorage.com>
- addressed review comments Signed-off-by: Ram <rsuradkar@purestorage.com>
- validate transform CR - dry-run on newly detected object before starting migration Signed-off-by: Ram <rsuradkar@purestorage.com>
Signed-off-by: Ram <rsuradkar@purestorage.com>
Signed-off-by: Ram <rsuradkar@purestorage.com>
Signed-off-by: Ram <rsuradkar@purestorage.com>
Signed-off-by: Ram <rsuradkar@purestorage.com>
Fixed a v1beta1 based getCRD call which will fail for k8s-1.22 or more because these APIs are removed in k8s-1.22 onwards. Signed-off-by: Lalatendu Das <ldas@purestorage.com>
Bumped up the go version required for gotestsum package Signed-off-by: Kesavan Thiruvenkadasamy <kthiruvenkadasamy@purestorage.com>
- With fix, we will include all the CRDs of a group, if one CRDs
of a parrticular group had a CR in the given namespace.
- added prepareMutatingWebHookForApply, prepareValidatingWebHookForApply, validatingWebHookToBeCollected and mutatingWebHookToBeCollected apis
is a generic backup.
- If the backup volume list had only non-kdmp volumes, trigger the
post exec rule after the startbackup API.
- If the backup volume list had only kdmp volumes or mix of both
kdmp and non-kdmp volume, we will call the post exec rule, once the volume backup is completed.
…rt in resourcecollector.
The image registry and namespace details are passed via CR. This is passed to JOB to determine the executor image location. Signed-off-by: Lalatendu Das <ldas@purestorage.com>
Review Comments Fixing - This is an unwanted file got created during some git operation, hence need to be deleted.
Signed-off-by: Kesavan Thiruvenkadasamy <kthiruvenkadasamy@purestorage.com>
all resources status
with timeout value.
…on also while restoring pvcs.
Signed-off-by: Kesavan Thiruvenkadasamy <kthiruvenkadasamy@purestorage.com>
For AWS , azure and GCP based volumes we will used kdmp driver to take a backup only when the the backuplocation type is NFS. Signed-off-by: Lalatendu Das <ldas@purestorage.com>
When Backuplocation type is NFS, then we will use KDMP driver to take backup for CSI volumes. Signed-off-by: Lalatendu Das <ldas@purestorage.com>
Collaborator
|
Can one of the admins verify this patch? |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1273 +/- ##
==========================================
- Coverage 68.47% 67.46% -1.02%
==========================================
Files 42 42
Lines 4628 4696 +68
==========================================
- Hits 3169 3168 -1
- Misses 1145 1211 +66
- Partials 314 317 +3
☔ View full report in Codecov by Sentry. |
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
8 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?
What this PR does / why we need it:
Does this PR change a user-facing CRD or CLI?:
Is a release note needed?:
Does this change need to be cherry-picked to a release branch?: