nfs-subdir-external-provisioner
csi-driver-nfs
Our great sponsors
nfs-subdir-external-provisioner | csi-driver-nfs | |
---|---|---|
45 | 5 | |
1,775 | 468 | |
5.5% | 7.5% | |
5.4 | 8.1 | |
10 days ago | 5 days ago | |
Shell | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nfs-subdir-external-provisioner
-
Help me What to Choose?
NFS Provisioner
-
Longhorn alternatives
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.
-
Move to K8s for hosting at home?
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.
-
Unsure how NFS Persistent Volumes work, please help!
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.
-
Almost 1yr in the making, finally got my Kubernetes DevOps/IaC/CD set up going, fully self-hosted cloud equiivalent. GLEE!!! (AMA?)
nfs-subdir-external-provisioner: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner
-
Network Storage on On-Prem Barebones Machine
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.
- Template like values in CSI manifest ${.PVC.namespace} and ${.PVC.name} ... Somebody give me some insight into these?
-
Longhorn to nas nfs
I have also used: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner for playing with NFS, directly from K8, instead of hosts.
-
K8s Persistant Storage
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.
csi-driver-nfs
- Self Hosted Kubernetes - Solving the Storage Problem
- K8s Persistant Storage
-
What's the best way to troubleshoot PVCs?
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
What are some alternatives?
longhorn - Cloud-Native distributed storage built on and for Kubernetes
dynamic-nfs-provisioner - Operator for dynamically provisioning an NFS server on any Kubernetes Persistent Volume. Also creates an NFS volume on the dynamically provisioned server for enabling Kubernetes RWX volumes.
synology-csi
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
csi-s3 - A Container Storage Interface for S3
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
kadalu - A lightweight Persistent storage solution for Kubernetes / OpenShift / Nomad using GlusterFS in background.
container-object-storage-interface-spec - Container Object Storage (COSI) Specification
restic - Fast, secure, efficient backup program
helm - The Kubernetes Package Manager
kustomize - Customization of kubernetes YAML configurations