Search code examples
kubernetesnfspersistent-volumesgoogle-persistent-disk

Is there a best practice when using nfs over GCEPersistentDisk?


I'm a software developer who got to a point where I need to mount a Persistent Volume with ReadWriteMany access mode in multiple nodes, in my GKE Cluster.

I'm well aware that GCEPersistentDisk does not support such access mode, so I turned to NFS instead.

My main question is what considered best practice to overcome this GCEPersistentDisk limitation?

I did a some research before posting this question, but I could not find a clear fit solution. Allow me to list some of the options found and their respective cons:

  • Nfs using helm chart - seems great but it's deprecated. Why? What's wrong with this method?
  • nfs-subdir-external-provisioner chart - requires an NFS server installed and I'm not sure how to. In addition it's pitfalls are a major concern.
  • Google Filestore - seems easy to use but its minimum size is 1 Tb which will result in expensive & major unused memory.
  • Turn to GlusterFs instead of NFS - seems complicated to install & maintain.

Many Thanks to all involved!


Solution

  • I eventually found out that you can mount GCS and then access blobs in it using: gcsfuse

    For future references - there are equivalents in s3fs-fuse (which supports also GCS, minio, etc).

    Sorry if I spammed.