Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Volume plugin dir #1

Closed
stiks opened this issue Jun 21, 2018 · 3 comments
Closed

Volume plugin dir #1

stiks opened this issue Jun 21, 2018 · 3 comments

Comments

@stiks
Copy link

stiks commented Jun 21, 2018

Basically volume plugin dir is not static, it depend on system itself. Some vendors may choose to change the directory due to various reasons. For example, GKE uses /home/kubernetes/flexvolume, and RKE uses /var/lib/kubelet/volumeplugins

User can find the correct directory by running ps aux|grep kubelet on the host and check the --volume-plugin-dir parameter. If there is none, the default /usr/libexec/kubernetes/kubelet-plugins/volume/exec/ will be used.

This is mainly FYI.

@fstab
Copy link
Owner

fstab commented Jun 21, 2018

The mount point is passed as the 1st parameter when Kubernetes calls cifs mount. So the Flexvolume plugin does not need to know how the volume-plugin-dir is configured, it just takes the mount point from the parameter. The mount point is not hard-coded in the script.

@stiks
Copy link
Author

stiks commented Jun 21, 2018

Install instruction requires to know where to put cifs file. mkdir -p will create that folder, but cifs will not work.

fstab added a commit that referenced this issue Jun 21, 2018
@fstab
Copy link
Owner

fstab commented Jun 21, 2018

Ah, I confused the volume plugin dir and the mount point. Thanks a lot for pointing this out and sorry for the confusion. I updated the README.

@fstab fstab closed this as completed Jun 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants