local-path-provisioner
Dynamically provisioning persistent local storage with Kubernetes (by rancher)
proxmox-k8s
By alexpdp7
| local-path-provisioner | proxmox-k8s | |
|---|---|---|
| 30 | 7 | |
| 2,007 | 15 | |
| 2.2% | - | |
| 6.1 | 0.0 | |
| 1 day ago | 7 months ago | |
| Go | Shell | |
| 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
proxmox-k8s
Posts with mentions or reviews of proxmox-k8s.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-12.
- Suggest container Linux distro go to deploy Kubernetes on a Bare Metal Server
-
My K8S installer now has an Ansible role for Proxmox
I've been working on a Kubernetes "installer" that creates an ISO derived from Fedora CoreOS that when booted from, installs Kubernetes. This can be found at https://github.com/alexpdp7/proxmox-k8s .
- Ansible playbook to provision a K8S cluster on Proxmox in about 10 minutes
- Personal project: a script to deploy a convenient single-node K8S cluster
- Suggestions for an Ingress controller
-
Single-node storage recommendations
So I'm setting up FCOS + k0S. I got the basic install working, but I don't have a fully operative setup.
- Which k8s are you using?
What are some alternatives?
When comparing local-path-provisioner and proxmox-k8s you can also consider the following projects:
sig-storage-local-static-provisioner - Static provisioner of local volumes
k3os - Purpose-built OS for Kubernetes, fully managed by Kubernetes.
topolvm - Capacity-aware CSI plugin for Kubernetes
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
csi-lib-utils - Common code for Kubernetes CSI sidecar containers (e.g. `external-attacher`, `external-provisioner`, etc.)
kairos - :penguin: The immutable Linux meta-distribution for edge Kubernetes.
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
os2 - EXPERIMENTAL: A Rancher and Kubernetes optimized immutable Linux distribution based on openSUSE
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
kusk-gateway - Kusk-gateway is an OpenAPI-driven API Gateway for Kubernetes
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
gateway-api - Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.
local-path-provisioner vs sig-storage-local-static-provisioner
proxmox-k8s vs k3os
local-path-provisioner vs topolvm
proxmox-k8s vs metallb
local-path-provisioner vs csi-lib-utils
proxmox-k8s vs kairos
local-path-provisioner vs kind
proxmox-k8s vs os2
local-path-provisioner vs nfs-ganesha-server-and-external-provisioner
proxmox-k8s vs kusk-gateway
local-path-provisioner vs csi-driver-nfs
proxmox-k8s vs gateway-api