nfs-subdir-external-provisioner
container-object-storage-interface-spec
Our great sponsors
nfs-subdir-external-provisioner | container-object-storage-interface-spec | |
---|---|---|
48 | 1 | |
2,358 | 58 | |
4.1% | - | |
4.2 | 2.1 | |
15 days ago | 8 months ago | |
Shell | Shell | |
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
-
Investigating a failed VolumeSnapshot with NFS on Kubernetes
Using nfs-subdir-external-provisioner instead of csi-driver-nfs
-
Database corruption
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.
-
Utilizing traditional storage in a modern way
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
-
Help me What to Choose?
NFS Provisioner
- [GUIDE] How to deploy the Servarr stack on Kubernetes with Terraform!
-
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.
-
Recommendations for k8s storage solution
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.
-
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.
-
K8s - Self hosted PaaS?
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.
-
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.
container-object-storage-interface-spec
What are some alternatives?
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
longhorn - Cloud-Native distributed storage built on and for Kubernetes
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
GlusterFS - Gluster Filesystem : Build your distributed storage in minutes
csi-s3 - A Container Storage Interface for S3
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
csi-driver-smb - This driver allows Kubernetes to access SMB Server on both Linux and Windows nodes.
kadalu - A lightweight Persistent storage solution for Kubernetes / OpenShift / Nomad using GlusterFS in background. More information at https://kadalu.tech
restic - Fast, secure, efficient backup program
helm - The Kubernetes Package Manager