local-path-provisioner
Dynamically provisioning persistent local storage with Kubernetes (by rancher)
topolvm
Capacity-aware CSI plugin for Kubernetes (by topolvm)
Our great sponsors
| local-path-provisioner | topolvm | |
|---|---|---|
| 30 | 3 | |
| 1,982 | 705 | |
| 3.3% | 5.4% | |
| 6.3 | 9.1 | |
| 21 days ago | 7 days ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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
Posts with mentions or reviews of local-path-provisioner.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-01-19.
-
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
topolvm
Posts with mentions or reviews of topolvm.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-29.
-
Linux LVM API for using python or Golang
I’m not aware of anything but you might want to look at the TopoLVM lvmd implementation. It’s a Kubernetes storage plugin for LVM and it talks to a interface daemon over gRPC so it might be useful inspiration at least.
-
How to format drives for local persistent volumes
there are local CSI-s like: https://github.com/topolvm/topolvm https://blog.min.io/introducing-directpv/
- Storage provisioner for self-created clusters in 2022, for disk-heavy workload like MySQL?
What are some alternatives?
When comparing local-path-provisioner and topolvm you can also consider the following projects:
sig-storage-local-static-provisioner - Static provisioner of local volumes
gemini - Automated backups of PersistentVolumeClaims in Kubernetes using VolumeSnapshots
csi-lib-utils - Common code for Kubernetes CSI sidecar containers (e.g. `external-attacher`, `external-provisioner`, etc.)
ceph-csi - CSI driver for Ceph
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
aws-ebs-csi-driver - CSI driver for Amazon EBS https://aws.amazon.com/ebs/
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
rook - Storage Orchestration for Kubernetes
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
csi-s3 - A Container Storage Interface for S3
proxmox-k8s
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
local-path-provisioner vs sig-storage-local-static-provisioner
topolvm vs gemini
local-path-provisioner vs csi-lib-utils
topolvm vs ceph-csi
local-path-provisioner vs kind
topolvm vs aws-ebs-csi-driver
local-path-provisioner vs nfs-ganesha-server-and-external-provisioner
topolvm vs rook
local-path-provisioner vs csi-driver-nfs
topolvm vs csi-s3
local-path-provisioner vs proxmox-k8s
topolvm vs secrets-store-csi-driver