local-path-provisioner
external-snapshotter
Our great sponsors
local-path-provisioner | external-snapshotter | |
---|---|---|
30 | 4 | |
1,982 | 433 | |
3.3% | 3.5% | |
6.3 | 8.8 | |
20 days ago | about 24 hours ago | |
Go | 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.
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
external-snapshotter
-
Question about PVC snapshots and architecture
By the way, I got that error very often - kubernetes-csi/external-snapshotter#300 - the fix is in progress. I'm afraid about the snapshot mechanism performance. It's also a question about the GCP snapshot mechanism, so I'm gathering opinions.
-
My completely automated Homelab featuring Kubernetes
VolSync is a much better option than Velero IMO, Velero was created before GitOps was a thing and it really tries to do too much when all I need is a reliable way to backup and restore PVCs. If your CSI supports volume snapshots, VolSync can use the snapshot-controller to create Volume Snapshots and then mount those as a PVC to a temporary pod to then backup that up to S3. This is really great for backing up PVCs because it's not backing them up from a running workload.
-
Backup solution for volumes
Is it required to store it to s3? If I were U i would use native approach https://kubernetes.io/docs/concepts/storage/volume-snapshots/ with https://github.com/kubernetes-csi/external-snapshotter
-
Amazon EKS and IRIS. High Availability and Backup
#Install CSI Snapshotter and CRDs kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/client/config/crd/snapshot.storage.k8s.io_volumesnapshotcontents.yaml kubectl apply -n kube-system -f https://github.com/kubernetes-csi/external-snapshotter/raw/master/client/config/crd/snapshot.storage.k8s.io_volumesnapshotclasses.yaml kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/client/config/crd/snapshot.storage.k8s.io_volumesnapshots.yaml kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/deploy/kubernetes/snapshot-controller/setup-snapshot-controller.yaml kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/deploy/kubernetes/snapshot-controller/rbac-snapshot-controller.yaml
What are some alternatives?
sig-storage-local-static-provisioner - Static provisioner of local volumes
csi-driver-smb - This driver allows Kubernetes to access SMB Server on both Linux and Windows nodes.
topolvm - Capacity-aware CSI plugin for Kubernetes
renovate - Universal dependency automation tool.
csi-lib-utils - Common code for Kubernetes CSI sidecar containers (e.g. `external-attacher`, `external-provisioner`, etc.)
home-ops - Wife approved HomeOps driven by Kubernetes and GitOps using Flux
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
cluster-template - A template for deploying a Kubernetes cluster with k3s or Talos
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
k8s_gateway - A CoreDNS plugin to resolve all types of external Kubernetes resources
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
volsync - Asynchronous data replication for Kubernetes volumes