spec icon indicating copy to clipboard operation
spec copied to clipboard

Container Storage Interface (CSI) Specification.

Results 126 spec issues
Sort by recently updated
recently updated
newest added

AWS customers would like to modify their volumes (e.g. increase IOPS, change volume type, etc.), but there is currently no way to do this through the CSI Spec. The current...

In the following scenario, could you please clarify the right behavior w.r.t ControllerPublishVolume call semantics: Setup: 0. Volume v1 is created with multi node reader/writer capability. 1. ControllerPublishVolume for node...

For example: Because of that when deleting volume, we want to know where is the storage( about the storage's URL、username and password for login storage), I think it's needed to...

With latest CSI spec, topology information is passed into `CreateVolume` call, so that CSI driver can provision a volume by the given `TopologyRequirement`. The topology requirement could be region, zones,...

It's better have a template for issues and PRs, we could refine the templates later. /assign @jdef @saad-ali

Here at NetApp we make heavy use of the CSI standards in order to implement the NetApp Trident CSI for our storage products. We are investigating how to support `snapshot...

While it is possible to do filesystem freeze/unfreeze using ExecutionHook when taking a snapshot, it requires elevated privileges on the pod. We are considering adding new NodeFreeze/UnfreezeVolumeFilesystem Node PRCs because...

Add new controller capability: * UNPUBLISH_FENCE Add new node capabilitiy: * FORCE_UNPUBLISH

### Problem Overview: ControllerPublishVolume has a contract to return FAILED_PRECONDITION with the status indicating the node id that the volume is currently published on. This helps detecting stale ControllerPublishVolume API...

"ControllerGetVolumeResponse should contain current information of a volume if it exists. If the volume does not exist any more, ControllerGetVolume should return gRPC error code NOT_FOUND" refer discussion : https://kubernetes.slack.com/archives/C8EJ01Z46/p1635513340016300...