spec
spec copied to clipboard
Container Storage Interface (CSI) Specification.
Updated few lines to make the meaning more explicit.
Based on #413 and CSI community meeting notes added on 2/11/20, This specific case with empty `capacity_range` was added to the `CreateVolumeRequest` errors table.
Also overload meaning of readonly expansion on node. xref https://github.com/container-storage-interface/spec/issues/423
In the ["Connectivity" section of the Protocol](https://github.com/container-storage-interface/spec/blob/master/spec.md#connectivity) the spec states: > Only UNIX Domain Sockets MAY be used as endpoints. This will likely change in a future version of this...
The spec says the following about the `snapshot_id` parameter to the `ListSnapshots` RPC: ``` // Identity information for a specific snapshot. This field is // OPTIONAL. It can be used...
Sometimes a CO may not accurately be able to verify if volume is already published to a node or not when calling `ControllerExpandVolume` RPC call and in that case an...
Nomad 0.11, now in beta, just added support for the CSI spec I believe. So it might be worth adding them to the list of supporting tools.
Reusing existing gRPC status codes leads to ambiguities for the CO. `RESOURCE_EXHAUSTED` can be returned by the gRPC transport layer, for example when message sizes are exceeded. Therefore a CO...
Assume that a `custom-pod` mounts the PVC by CSI-plug-in, the CSI-plug-in-sidecar may fail due to some reason and the mount in `custom-pod` fails even after the CSI-plug-in is restarted. What...