Hemant Kumar

@humblec if we have a valid `targetPath` - do we still need to verify if `targetPath` belongs to given volume ID? Does this apply to something like `NodeUnpublishVolume` too -...

I am sort of becoming convinced that we may have to add secrets here. The other case I think is, this call is also being used to report volume health...

Why does SP needs to evaluate the path at all? Can you explain the reasoning little bit? Or to rephrase - can SP work with given path in these API...

Thanks for clarifying this @bswartz . I have been thinking some more about it and for `NodeGetVolumeStats` call at least - CO must keep track of the information that path...

I have been thinking some more about this and I think that - removing/deprecating plugin level online/offline capability is fine. Pros: 1. Since no CO actually uses this capability, removing...

Just to clarify - we are **not removing** offline capability. Volumes can be still expanded offline but what we are talking about removing/deprecating is, ability for a plugin to declare...

Spoke with @cduchesne offline on slack and their use case is to support expansion on node, after `NodeStage` but before `NodePublish`. This is already supported and we discussed if a...

To follow up on action items: 1. readonly and `NodeExpandVolume` changes are in - https://github.com/container-storage-interface/spec/pull/431 2. online and offline plugin capabilities deprecated - https://github.com/container-storage-interface/spec/pull/429 Currently both builds are failing for...

cc @jingxu97 @jsafrane @msau42

There is lot of gray areas in: > In some cases, a CO MAY NOT be able to cancel a pending operation because it depends on the result of the...