-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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
Move VolumeSnapshotDataSource feature gate check from validation #72666
Conversation
Hi @rajathagasthya. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @liggitt |
/ok-to-test |
414f9d3
to
bbdce5c
Compare
FYI, please don't reference the issue in the commit message like rajathagasthya@414f9d3, github spams issues mercilessly any time the commit is pushed anywhere |
Ugh, sorry for the notification spam! |
cc @msau42 |
bbdce5c
to
88abcb7
Compare
/approve will leave to @kubernetes/sig-storage-api-reviews for lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, rajathagasthya The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-kubernetes-integration |
1 similar comment
/test pull-kubernetes-integration |
/lgtm |
/retest |
1 similar comment
/retest |
#71696 failure |
ridiculous |
:/ |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Moves feature-gate checking of VolumeSnapshotDataSource out of validation into the strategy utility methods, and avoids dropping data on update if the existing PVC Spec already used DataSource. Adds unit test for the strategy utility method and updates validation test.
Which issue(s) this PR fixes:
xref #72651
Does this PR introduce a user-facing change?:
/sig api-machinery
/sig storage