jdef

At first glance, this seems like a breaking change to the spec. As this (CSI) is not a k8s project, it is not bound by the referenced KEP. That said,...

Thanks @tgross. Are there any concerns from plugin providers that may be relying on CSI-as-written vs. the best-effort described herein? Also Mesos is another CO w/ CSI integration - anyone...

This sounds like an issue that should be filed against some k8s project, not the general CSI spec. On Tue, May 28, 2019, 2:36 AM alexanderKhaustov wrote: > For a...

The controller-unpublish call does not relay state on purpose. Consider that the CO is braindead and loses context. It should still be possible to unpublish. I'm sympathetic to the partitioning...

The only required field for controller-unpublish is volume_id. On Fri, Nov 5, 2021, 6:40 PM Sumukh Shivaprakash ***@***.***> wrote: > Isn't the co storing/plumbing around the volume id and volume...

Correct. A human should be able to provide volume ID. On Fri, Nov 5, 2021, 7:02 PM Sumukh Shivaprakash ***@***.***> wrote: > Unless you are referring to manual intervention by...

CO must do more: There's another csi proposal that deals with partitioning and attempts to implement a fencing strategy within csi - I commented there as well. The CO bears...

Not sure why I'm pinged here. Afaict this issue / ticket has been settled. On Tue, Nov 9, 2021, 12:27 AM Sumukh Shivaprakash ***@***.***> wrote: > @jdef - gentle ping!...

I think I misread the original proposal, mistakenly confusing volume-context for publish-context. That said... "etag" sounds like additional state that: (a) CO would need to track/remember as a result of...

Kindly submit a PR. If this is your first, you probably need to sign the CLA, otherwise PR cannot be accepted. On Tue, Nov 9, 2021, 10:44 AM Sumukh Shivaprakash...