It'll be changed so flexvolume plugins attach/detach/mount/unmount function will be tied to the attacher/detacher/mounter/unmounter interfaces. This means that the attach/detach function can be executed by any host while the mount/unmount function will be executed by the kubelet on the target host.
When the flexvolume changes (https://github.com/kubernetes/kubernetes/issues/20262) will land the torusblk flex implementation must be changed to move the attach/detach function inside the mount/unmount functions since the volume attachment/detachment have to be executed by the kubelet on the target host.
If you're ok I'll open a PR when the k8s changes (maybe in k8s 1.3) will land.
In kubernetes/kubernetes#20262 a new attach/detach controller will be introduced and starting from this comment https://github.com/kubernetes/kubernetes/issues/20262#issuecomment-223254349 there're more details on how it works and the future of the flexvolume plugin executor.
It'll be changed so flexvolume plugins attach/detach/mount/unmount function will be tied to the attacher/detacher/mounter/unmounter interfaces. This means that the attach/detach function can be executed by any host while the mount/unmount function will be executed by the kubelet on the target host.
When the flexvolume changes (https://github.com/kubernetes/kubernetes/issues/20262) will land the
torusblk flex
implementation must be changed to move the attach/detach function inside the mount/unmount functions since the volume attachment/detachment have to be executed by the kubelet on the target host.If you're ok I'll open a PR when the k8s changes (maybe in k8s 1.3) will land.