diff options
| author | Yaniv Kaul <ykaul@redhat.com> | 2017-08-24 11:36:08 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-08-24 11:36:08 +0300 |
| commit | 8a5c032aefc80b837933b19aa2ad0e05bfb29f00 (patch) | |
| tree | c86cfb734f77ddffb0e070404a5bebac0eb5b7d4 | |
| parent | cc0b7b8f1ccb3ef7a5628f8482f82613ddd74175 (diff) | |
Remove getvolumes, as it is not supported and ignored
Based on discussion on kubernetes-sig-storage:
2. Some drivers implemented getvolume, some didn't[4]. Is it expected to be a name of an existing volume on the storage? Can nodename+volumename be considered unique?
[Chakri] GetVolumeName is not supported and is ignored. You don’t have to implement it.
| -rw-r--r-- | contributors/devel/flexvolume.md | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/contributors/devel/flexvolume.md b/contributors/devel/flexvolume.md index 41d7e54c..8ba55770 100644 --- a/contributors/devel/flexvolume.md +++ b/contributors/devel/flexvolume.md @@ -27,13 +27,6 @@ See [Driver output](#driver-output) for the capabilities map format. <driver executable> init ``` -#### Get volume name: -Get a cluster wide unique volume name for the volume. Called from both Kubelet & Controller manager. - -``` -<driver executable> getvolumename <json options> -``` - #### Attach: Attach the volume specified by the given spec on the given host. On success, returns the device path where the device is attached on the node. Nodename param is only valid/relevant if "--enable-controller-attach-detach" Kubelet option is enabled. Called from both Kubelet & Controller manager. |