What are people using for storage on their resource constrained home #kubernetes clusters (lab)?
Currently using longhorn for ease of use. But would like lighter and even simpler. Need all nodes to access shared data. NFS could work, but heard bad things. Don’t see a lot of good info on s3 compatible. I imagine smb would suck. I’m sure I’ll stay where I am. But lazy google I guess. (Even though I have been) #k8s #storage #homelab

@bashfulrobot I've used NFS on a GKE cluster I was playing with. It's okay when it works, but when it doesn't, things go wrong very quickly.

Using s3fs would be my choice if I decided to revisit this. Plus most providers have their own s3-compatible services you can plug into this (S3 for AWS, GCS for GCP, etc)

@blenderfox I haven’t looked at fuse lately. I wonder what the performance would be like. I came across an s3proxy (to the file system) that I could run on a Vm to provided and s3 target. What would drive you this way?

@bashfulrobot performance is variable. If you're running s3fs from your homelab to AWS/GCP/Azure then everything gets transferred to and from the cloud, leading to slight lag (e.g. mounting then doing a ls will result in a noticable delay before you get the listing back)

Also note that you may be charged by the provider for the transfer.

As for s3proxy, I assume it's more or less the same as s3fs but without mounting a folder? (I've not used that so I don't know too much about it)