container-object-storage-interface-spec VS nfs-ganesha-server-and-external-provisioner

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.

Conceptually to attach your storage to your pod, you have to go through 2 objects, the PVC that attaches to the PV, which itself must have a physical support, so the nfs mount on your nodes in hostpath, which is globally disgusting, it is better to inform the NFS server in your PV. Maybe I'm wrong but it seems clear to me. However, if you ask this kind of questions, you might be missing two or three things about K8. I advise you to read the documentation about PV, PVC, SC etc... Also NFS is not POSIX and by nature slow, which can cause inconsistencies in your data, but this is an extreme case. In a logic of automation you can use this: https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner Help yourself with this . https://www.linuxtechi.com/configure-nfs-persistent-volume-kubernetes/

I found something similar that seems to be a continuation of the nfs-server-provisioner- https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner