local-path-provisioner
nfs-ganesha-server-and-external-provisioner
Our great sponsors
local-path-provisioner | nfs-ganesha-server-and-external-provisioner | |
---|---|---|
30 | 5 | |
1,982 | 394 | |
3.3% | 2.0% | |
6.3 | 3.1 | |
19 days ago | 3 months ago | |
Go | 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.
local-path-provisioner
-
Deploy Ghost with MySQL DB replication using helm chart
Deploy local-path-provisioner storage class but it does not support readwritemany so for high availability of your Kubernetes cluster better to use longhorn
-
lvp: Local Volume CSI Provisioner -- Dynamic PV Provisioning for your Home Cluster
I use this one. I'm waiting for the day it's combined with syncthing to sync across all nodes. https://github.com/rancher/local-path-provisioner
-
issues with pv retaining data on local-path SC
So I have this single node k3s cluster. k3s uses local-path (https://github.com/rancher/local-path-provisioner) as default SC that allows one to create dynamic volumes using nodes local storage.
-
How to format drives for local persistent volumes
Just create 1 single partition and format it with whatevery filesystem you like. And then use ranchers local-path-provisioner which will create a folder per PV (k3s has this integrated by default).
-
Persisting data in a dynamic volume?
Tinkering locally with local path provisioner (https://github.com/rancher/local-path-provisioner), I find that I can delete and re-create the pod, and the data persists on disk. However, if I delete the PVC, when I recreate the PVC, a new directory on disk is created.
-
Issues with "victoria-metrics-k8s-stack", monitoring k8s targets
It is better to use https://github.com/rancher/local-path-provisioner (or similar) for this case which will do PVC on local directories because manually linking PV<>PVC will not work.
-
single node k8s on nuc - homelab/prod - storage question
Since you only have one physical node anyway, I would just make the cluster a single-node cluster (1 VM) and use local storage on that VM. I’m biased though because this is what I do (I run K3s and use local path provisioner).
-
Using local disks for both K8s workloads, and exporting via SMB?
Rancher's Local Path Provisioner - From reading, seems to just use HostPath or Local PVs under the hood, but adds dynamic provisoning
-
Kubernetes: How to Persistent Storage
With any of those tools, you'd implement a network storage on top of a network storage. I would go with mouting few volumes per node +local storage like (https://github.com/rancher/local-path-provisioner).
- There doesn't seam to be any good distributed block storage for Kubernetes
nfs-ganesha-server-and-external-provisioner
- Alternative to Longhorn RWX?
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 2/2
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:
-
How to scale nginx pod when pod is mounting a volume
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.
-
NFS volume mount on Kubernetes
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/
-
NFS server provisioner deprecated - what's the replacement?
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
What are some alternatives?
sig-storage-local-static-provisioner - Static provisioner of local volumes
nfs-subdir-external-provisioner - Dynamic sub-dir volume provisioner on a remote NFS server.
topolvm - Capacity-aware CSI plugin for Kubernetes
longhorn - Cloud-Native distributed storage built on and for Kubernetes
csi-lib-utils - Common code for Kubernetes CSI sidecar containers (e.g. `external-attacher`, `external-provisioner`, etc.)
csi-s3 - A Container Storage Interface for S3
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
GlusterFS - Gluster Filesystem : Build your distributed storage in minutes
proxmox-k8s
helm-charts - Prometheus community Helm charts