jdef
jdef
I tend to agree that the application + OS bear most of the responsibility here. It's not clear to me that CSI should make any guarantees w/ respect to "flush...
is this related to #30 #99 ?
This has come up before and has been rejected. Can you explain your use case in more detail? On Fri, Nov 22, 2019 at 4:21 AM Louis Koo wrote: >...
We've been down this road before. I don't see any new, compelling reason to add secrets here. It should always be possible to unpublish/unstage regardless of secrets. If you need...
My interpretation of the slack thread is that maybe some k8s logic change is required. I don't agree with the proposal to change the spec here. Whether or not volume...
My interpretation of the slack thread is that k8s makes certain decisions based on results of list-volumes in conjuction with results from subsequent get-volume calls. What prevents that logic from...
This repo is for the CSI specification; if you want help w/ this issue, please contact Kubernetes SIG Storage which maintains the Kubernetes CSI implementation.
I'm not 100% clear on the use case for this. There are secrets for use w/ calls pertaining to singular volumes/snapshots. This looks like it might be the first place...
> I'm not 100% clear on the use case for this. There are secrets for use w/ calls pertaining to singular volumes/snapshots. This looks like it might be the first...
Thanks for the PR. The templates seem a bit k8s-centric, and this is not a k8s project. Nor does it use k8s PR robots. I'm open to the idea of...