kadalu VS nfs-subdir-external-provisioner

https://github.com/kadalu/kadalu/ is mentioned in https://github.com/kubernetes/kubernetes/issues/100897

Right now im just mounting NFS to my worker nodes and then using docker volumes for storage, i have seen this https://github.com/kadalu/kadalu but i havent gotten around to trying it

For gluster you can check out https://github.com/kadalu/kadalu. I tried but ultimately went back to host-mounted gluster: for some reason they chose to implement their controller in Python and it uses a lot of memory. Too much for my Pi’s.

Kadalu Storage is an opinionated distribution of GlusterFS. Kadalu Storage is light weight solution based on GlusterFs, that eliminates may layers(Glusterd) and integrate directly with Kubernetes APIs.

Kadalu, a distributed persistent storage solution like longhorn, is available on ARM: https://github.com/kadalu/kadalu

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

I am trying to run sonarr inside my k3s cluster. Since I have multiple nodes, in order to keep data persistant I have been using a NAS and the Kubernetes NFS external provisioner as my Storage Class.

There's this, if you want your nfs storage available to pods as PVCs, with some limitations: https://github.com/kubernetes-sigs/nfs-subdir-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 first installed a NFS Server via this helm chart: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner Eventually I deployed Longhorn cause I needed expandable volumes, which the first repo doesn't support. I guess for best performance you should go for a ceph cluster, but I'm not an expert.

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.

However, is it too difficult to create new pods/deployments etc on your own? I find it super easy to just create a PVC (via https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner ) and create a MySQL pod in a new namespace for every micro service I create.

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.