3 ms·
> Those two should give a good overview of the available options. Basically, you can use local paths, NFS shares, vendor-specific storage (e.g. AWS EBS) and var
by creshal 10y ago
> Those two should give a good overview of the available options. Basically, you can use local paths, NFS shares, vendor-specific storage (e.g. AWS EBS) and various other things.
Yeah, but which of them actually work?
- ThePhysicist 10y agoIt depends on the environment: If you're on AWS, you can use EBS, if you have an NFS share you can use that. In the simplest case, you can just a `hostPath` volume to mount a local directory from the pod's host.
- cies 10y ago> Yeah, but which of them actually work? And on top of that, which of them work when scaling the app out. In other words: how does each option deal with having multiple containers mount it. edit: From this link -- http://kubernetes.io/docs/user-guide/volumes/#types-of-volumes http://kubernetes.io/docs/user-guide/volumes/#types-of-volum... -- I found that the following volumes allow mounting by multiple writers: nfs, glusterfs and cephfs. But which one of these works well under (production) load?
- db48x 10y agoThere is no single "production load"; everyone's load is different, so you'll have to try it and measure. This is always the case with any storage system.
- justinsb 10y agoIf you're on GCE or AWS, GCE PDs or AWS EBS works out-of-the-box (i.e. using kube-up, kops or kube-aws on AWS, kube-up or GKE on GCE). Everything should work, but it's harder to validate / work around every NFS server's possible set of configuration options (for example).