local-path-provisioner
helm-charts
Our great sponsors
local-path-provisioner | helm-charts | |
---|---|---|
30 | 11 | |
1,994 | 278 | |
3.9% | 5.4% | |
6.1 | 9.4 | |
7 days ago | 10 days ago | |
Go | Mustache | |
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
helm-charts
-
Issues with "victoria-metrics-k8s-stack", monitoring k8s targets
https://github.com/VictoriaMetrics/helm-charts/commit/128d2a7fa23c717e780655f03df83b03e3d637ac could be the reason
-
Easy Prometheus/Grafana Setup With Dashboards Repo
There is also victoriametrics-operator and victoriametrics k8s stack helm chart.
-
Centralize Prometheus: Bad Practice?
BTW, you can use victoria-metrics-k8s-stack as a drop-in replacement for kube-prometheus-stack.
-
What do you guys use to manage/monitor multiple clusters?
It is possible to replace kube-prom-stack with VictoriaMetrics stack in every k8s cluster - see https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-k8s-stack/README.md
- Kubernetes Cluster uses a lot of RAM o.O
-
Server metrics
I'm monitoring CPU, memory, disk, network usage etc, the basic stuff available from kubernetes metrics via api. I also have a sidecar pod to send CPU temperature via opentsdb endpoint of Victoria Metrics. I run this helm chart which has operator and db - it can be added to grafana as a Prometheus data source.
-
Custom application monitoring with Victoria Metrics in k8s
There is a k8s stack Helm Chart which can provide the same functionality. Also check VictoriaMetrics Operator docs and our guides .
-
What is a simple, free monitoring tool for a Kubernetes cluster?
For metrics there is VictoriaMetrics operator and helm chart, which can be used for monitoring Kubernetes. See this guide.
What are some alternatives?
sig-storage-local-static-provisioner - Static provisioner of local volumes
lens - Lens - The way the world runs Kubernetes
topolvm - Capacity-aware CSI plugin for Kubernetes
agent - Vendor-neutral programmable observability pipelines.
csi-lib-utils - Common code for Kubernetes CSI sidecar containers (e.g. `external-attacher`, `external-provisioner`, etc.)
operator - Kubernetes operator for Victoria Metrics
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
helm-charts - Prometheus community Helm charts
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database