Codecov Report

Merging #1076 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1076       /-   ##
==========================================
  Coverage   34.16%   34.19%    0.03%     
==========================================
  Files          36       36              
  Lines        2901     2901              
==========================================
  Hits          991      992        1     
  Misses       1807     1806       -1     
  Partials      103      103

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1a39fd7...a2c233f. Read the comment docs.

Any idea when this will be merged?

Hello @hpbieker,

What was your intended use of the VFS plugin? For the most part we are using it for comprehensive end-to-end testing of the CSI plugins without a dependency on a backend storage platform. Any more info here would be great to here.

@clintkitson. I am looking for a way to utilize a cifs network file system for my Docker volumes. I know I can use the local volume driver and mount the cifs file system in each container. However, this means that I will have to include the username and password in the docker-stack.yml file for each service. I was hoping to just define a volume driver that could have predefined the authentication to my cifs file store.

I guess this would be possible by using the vfs driver. Preferably, there is a cifs driver similar to the nfs driver so that the mounting of the cifs drive is handled automatically. I guess it is just a matter of generalization of the nfs driver.

What does "predefined the authentication to my cifs file store" mean?

@clintkitson Sorry for the bad wording. I mean that I do not want to specify a username, password, hostname and path each volume I create. I think this should be a part of the configuration of the volume driver.