1.7 KiB
FlexVolume Driver
As the spec [1] introduced, FlexVolume [2] driver will implement the driver interfaces of FlexVolume plugin to enable Kubelet to consume persistent volumes. Each driver will be loaded when Kubelet starts and be used as the standalone FlexVolume plugin, which means that Kubelet may start several FlexVolume plugins and each plugin binds one driver.
In Fuxi-kubernetes, FlexVolume driver consists of four components.
1. Driver: FlexVolume plugin will communicate with driver by 'call-out'. So, for plguin, the driver should be an executable file which receives each command and returns corresponding results. For Cinder and Manila, there is a shell file for each of them to do this work respectively.
2. Server: The real driver runs as a service and locates at the work node. It calls Cinder and Manila to supply volume for Pod.
3. Client: 'Driver' will pass the commands to 'Service' via 'Client'.
4. Host: The driver runs on the node which may be baremetal or vitual machine. It needs to know the informations of work node to supply volume for Pod. 'Host' stands for the work node and supply relevant informations, such as host name, connector which is used to connect volumes.
References
_`[1]`: https://docs.openstack.org/developer/kuryr-kubernetes/specs/pike/fuxi_kubernetes.html
_`[2]`: https://github.com/kubernetes/community/blob/master/contributors/devel/flexvolume.md