nfs-subdir-external-provisioner VS nfs-ganesha-server-and-external-provisioner

NFS Provisioner

Depends on how much resiliency you need . Something like https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner works well for a lab or non-prod cluster. You could even use something like this in prod if you have access to highly reliably NFS mounts.

I used the NFS provisioner for persistent volumes until I got the Ceph side up and running. I created a share on my NAS specifically for k8s. It worked very well and had the bonus of being just a regular file system that you could browse/edit easily (just place files in or edit config). I would agree with not moving plex into k8s. I right now just have a barebones 1 control 2 worker setup using k3s.

This is what you need https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner Point it to a folder and it will create subfolders for each PVC.

nfs-subdir-external-provisioner: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner

With NFS I was able to get that to work using NFS SubDir Provisioner and this is working fine as far as I can tell. Though it is odd how it works. You dont seem to be able to tell the exact path you're going for, so you have to create a provisioner that goes to the path directly and even it will create its own folder with a GUI associated to it. This really isnt idea for things like scripted backups, or even knowing how persistence works properly.

I have also used: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner for playing with NFS, directly from K8, instead of hosts.

Then nfs is the way to go. Im using this one https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner at home with k3s. works fine for my usecases. I havent tested snapshots and restores yet.

Now, for the purposes of this article, in case you don't have an NFS server available, we will use a simple NFS Server Provisioner, which we'll use only for example purposes. As mentioned before, using a managed solution from a cloud provider or a properly configured HA NFS server in your infrastructure is highly recommended. We'll install not the most up-to-date solution, but it should work for example purposes. We will follow the Quickstart found in the repo, mixed with this repo which does some small tweaks to make it work with K3d, which is summarized in the following commands run from the helm folder:

Some people just setup an NFS share. There's one that uses existing NFS and another that also provides NFS. This becomes a single point of failure though.