Unverified Commit 332ea9da authored by Kubernetes Submit Queue's avatar Kubernetes Submit Queue Committed by GitHub

Merge pull request #57989 from NickrenREN/spec-0.1

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Bump CSI spec version to v0.1.0 **What this PR does / why we need it**: Update CSI spec dependency to point to v0.1.0 tag **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes # **Special notes for your reviewer**: **Release note**: ```release-note Update CSI spec dependency to point to v0.1.0 tag ``` /assign @saad-ali cc @lpabon
parents 57888103 13a30bfc
......@@ -437,7 +437,7 @@
},
{
"ImportPath": "github.com/container-storage-interface/spec/lib/go/csi",
"Rev": "ec298903f94e1d6d954de121b28044a2e1fdbf48"
"Rev": "9e88e4bfabeca1b8e4810555815f112159292ada"
},
{
"ImportPath": "github.com/containerd/containerd/api/services/containers/v1",
......
......@@ -73,9 +73,11 @@ type VolumeCapability_AccessMode_Mode int32
const (
VolumeCapability_AccessMode_UNKNOWN VolumeCapability_AccessMode_Mode = 0
// Can be published as read/write at one node at a time.
// Can only be published once as read/write on a single node, at
// any given time.
VolumeCapability_AccessMode_SINGLE_NODE_WRITER VolumeCapability_AccessMode_Mode = 1
// Can be published as readonly at one node at a time.
// Can only be published once as readonly on a single node, at
// any given time.
VolumeCapability_AccessMode_SINGLE_NODE_READER_ONLY VolumeCapability_AccessMode_Mode = 2
// Can be published as readonly at multiple nodes simultaneously.
VolumeCapability_AccessMode_MULTI_NODE_READER_ONLY VolumeCapability_AccessMode_Mode = 3
......@@ -1344,6 +1346,8 @@ type NodePublishVolumeRequest struct {
// The path to which the volume will be published. It MUST be an
// absolute path in the root filesystem of the process serving this
// request. The CO SHALL ensure uniqueness of target_path per volume.
// The CO SHALL ensure that the path exists, and that the process
// serving the request has `read` and `write` permissions to the path.
// This is a REQUIRED field.
TargetPath string `protobuf:"bytes,4,opt,name=target_path,json=targetPath" json:"target_path,omitempty"`
// The capability of the volume the CO expects the volume to have.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment