csi-driver-nfs VS synology-csi

Using nfs-subdir-external-provisioner instead of csi-driver-nfs

Probably you are looking for dynamic volume provisioning. Using this option you only need to create a persistent volume claim. The storage designed to your container. Instead of first creating a persistent volume and binding it to a pvc. Nowadays is common to use plugins CSI plugins for different storages backends. This repository contains some examples on how to mounts the NFS server on kubernetes and also create storage classes, and the CSI installation. It is worth to read the documentation due to the many concepts involved and details of importance like reclamation polices.

Depending on the use case, nfs could be a solution also. I have a k3s cluster on a nuc, and it works correctly https://github.com/kubernetes-csi/csi-driver-nfs

For nfs with k8s, you could use this https://github.com/kubernetes-csi/csi-driver-nfs

I‘m using https://github.com/SynologyOpenSource/synology-csi

There is a rather official storage connector for K8s and Syno: https://github.com/SynologyOpenSource/synology-csi

Some appliances provide CSI plugins just for that, eg. Synology: https://github.com/SynologyOpenSource/synology-csi If it does not apply to you, I'd still vote for B

What NAS storage do you have? Does a CSI driver exist for it? For example there's https://github.com/SynologyOpenSource/synology-csi for Synology NAS, no idea how well it works.

I dont think so. It wouldn't make sense to use NAS for k8s cluster. Although you could use it for cluster storage - https://github.com/SynologyOpenSource/synology-csi

Recently I also discovered: https://github.com/SynologyOpenSource/synology-csi but havent used it yet to benchmarking.

NFS provisioner. Or you could try synology csi driver (https://github.com/SynologyOpenSource/synology-csi)