-
Notifications
You must be signed in to change notification settings - Fork 199
Enhance CNS Unregister Volume API to refer to K8s metadata instead of CNS metadata #3304
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
Enhance CNS Unregister Volume API to refer to K8s metadata instead of CNS metadata #3304
Conversation
|
Hi @kolluria. Thanks for your PR. I'm waiting for a kubernetes-sigs 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-sigs/prow repository. |
f3f5cb7 to
4edb6df
Compare
|
/ok-to-test |
divyenpatel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: divyenpatel, kolluria 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 |
What this PR does / why we need it:
Enhances CNS Unregister Volume functionality by removing the dependency on the less reliable
cns volume metadataand using the kubernetes cluster as the source of truth.Testing done:
Environment
When volume is unused
Result: volume got unregistered successfully
When volume is in use by a pod
Result: unregistration failed successfully
When volume is in use by a VM
Result: unregistration failed successfully
When a volume is created from TKC but not used by a pod
Result: volume got unregistered successfully
When volume is created from TKC and is in use by a TKC pod
Result: unregistration failed successfully
Release note: