Possibility of using gluster volume in k8s if glusterfs client package on container

Kubernetes supports several types of Volumes including GlusterFS. Also GlusterFS can be Persistent Volumes in k8s.

For using glusterfs volumes in k8s, one of prerequisites is “Install Glusterfs client package on the Kubernetes nodes”. But if it is expect that everything shall be in containers. Is that possible that put gluster client in container (e.g. DaemonSet deploy gluster client on k8s node first), while k8s still can suing glusterfs as above example?

  • docker container network/DNS/Firewall issue
  • apache-spark startup error on alpine linux docker
  • Running command in a docker
  • No space left for new subnet when Docker network get address from Flannel
  • Ports are blocked: Can't install Docker Universal Control Plane on Ubuntu guest using VMware
  • Docker registry mirror not saving images with minikube
  • Will k8s support such using scenarios?

  • `initialize': the scheme postgres does not accept registry part: postgres:@ (or bad hostname?) (URI::InvalidURIError) with Docker
  • Docker rails migrations
  • Nightwatch inside Docker only works with Phantom
  • Docker won't publish selected ports
  • docker-compose keeps using old image content
  • docker + haproxy on mac 10.11.5 doesn't work
  • One Solution collect form web for “Possibility of using gluster volume in k8s if glusterfs client package on container”

    Nothing is officially supported via the way you described at the moment, but take a look at this blog post, it outlines exactly what you describe: https://huaminchen.wordpress.com/2016/03/22/yet-another-containerized-mounter-for-kubernetes/

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.