3 ms·
You are able to attach the block devices, but local file systems do not support being mounted on more than one host. For that you need to use a cluster file sy
by fh973 6y ago
You are able to attach the block devices, but local file systems do not support being mounted on more than one host.
For that you need to use a cluster file system, but that's a different beast.
- antonvs 6y agoThe multi-reader scenario definitely supports multiple readers of the same file system - we use it both in and out of Kubernetes on GCP. Kubernetes has specific support for this with its ReadOnlyMany access mode: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes https://kubernetes.io/docs/concepts/storage/persistent-volum... However, I do see on that page that AWS EBS doesn't support this mode, so perhaps that's what you're thinking of.
- hardwaresofton 6y agoWould you mind going into detail on your setup? What do you use to do this outside and inside GCP?
- antonvs 6y agoBoth scenarios I was referring to are on GCP, but one is on k8s (GKE) and one uses ordinary GCP VMs. In both cases we're using the multi-reader mounting feature of GCP persistent disks, all that changes is how that's specified. Outside GCP, we do have an on-premise product that can deploy on any k8s cluster. In that case, the default is for the customer to provide an NFS mount for the data in question. We use the same k8s ReadOnlyMany access type for that.