Hey everyone! I'm setting up my k3s (Kubernetes) cluster at home and currently using Longhorn for my persistent volumes, which are stored on local SSDs (256GB each). I have a separate Docker host that runs an "arr" stack, and I'm planning to migrate that to the k3s cluster. To manage more data than what my SSDs can provide, I want to mount external storage using NFS. Now, here's my dilemma: Since I'll likely use NFS anyway, would it make sense to ditch Longhorn completely and store my volumes on NFS instead? This might simplify the installation process for my cluster, especially since I regularly rebuild it as I learn more about Kubernetes.I think this would also mean I wouldn't have to go through the extra steps of restoring volumes via Longhorn and Velero since NFS would just let me mount them directly, right? Let me know what you think!
1 Answer
You've got a couple of concerns with switching to NFS. First, if your NFS storage isn't redundant, any issue with your NFS server could potentially bring down your entire cluster. That's a big risk for production environments. Second, if you have any SQLite databases, running those over NFS can lead to corruption issues—definitely something to think about if you're using non-cloud-native apps.
Thanks for your feedback! I'm considering using TrueNAS for this. It wouldn't be redundant, but I'd have solid SSDs. With TrueNAS, I could also offer S3 or iSCSI. Would that limit some risks?