-
Notifications
You must be signed in to change notification settings - Fork 375
Add GetSnapshot RPC #586
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
base: master
Are you sure you want to change the base?
Add GetSnapshot RPC #586
Conversation
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.
/lgtm
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.
Looks good to me, thanks! You probably want to squash the commits into one before it gets merged?
Squashed the commits. |
See-also: container-storage-interface/spec#586 Signed-off-by: Niels de Vos <ndevos@ibm.com>
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.
Thanks!
It has obviously been an omission, and I can imaging COs would want to use this. Can you leave a link in the comments where this new procedure would be used?
It's expected that statically provisioned group snapshots would use this API to populate information about the individual members of the group snapshot. Today we don't have a good way of getting the necessary information in that case. One hack is to rely on ListSnapshots with a snapshot ID passed in, but many drivers don't support that, due to other challenges related to snapshot listing. |
Is there a KEP that describes the use case? Unclear why the list API
doesn't work here.
James DeFelice
…On Mon, Apr 28, 2025, 1:12 PM Ben Swartzlander ***@***.***> wrote:
*bswartz* left a comment (container-storage-interface/spec#586)
<#586 (comment)>
Thanks!
It has obviously been an omission, and I can imaging COs would want to use
this. Can you leave a link in the comments where this new procedure would
be used?
It's expected that statically provisioned group snapshots would use this
API to populate information about the individual members of the group
snapshot. Today we don't have a good way of getting the necessary
information in that case. One hack is to rely on ListSnapshots with a
snapshot ID passed in, but many drivers don't support that, due to other
challenges related to snapshot listing.
—
Reply to this email directly, view it on GitHub
<#586 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR5KLGNAPRZ6P7SBB5IDOD23ZOOBAVCNFSM6AAAAAB3JY3BXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMZVHEZDSNZYGY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Here is the KEP: https://github.com/kubernetes/enhancements/pull/5013/files |
What type of PR is this?
feature
What this PR does / why we need it:
This PR adds a GetSnapshot RPC
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce an API-breaking change?: