local-path-provisioner
cost-model
local-path-provisioner | cost-model | |
---|---|---|
30 | 15 | |
2,003 | 2,192 | |
2.2% | - | |
6.1 | 9.7 | |
5 days ago | almost 2 years 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
cost-model
-
7 Kubernetes Companies to Watch in 2022
Kubecost gives you insight into where your Kubernetes spend is going. You can view your spend per namespace, service, or even team, and you can set budgets and get real-time alerts. Kubecost can also track other cloud spend from things like RDS and S3, and it also works with on-prem k8s clusters. Kubecost also offers an open source version.
-
Interesting tools?
kubecost - analyse cost of the cluster https://kubecost.com/
- OpenSourec & On-Prem Cost-Tracking for K8s
-
Twelve Years of Go
> No inheritance - no more digging through the massive world-tree of objects to find the code that actually does things.
That's not 100% accurate; as a concrete example, tell me which files (to say nothing of the actual downstream types!) contain the implementations of this interface method: https://github.com/kubecost/cost-model/blob/v1.88.0/pkg/clou... (err, without using github's fancy new SourceGraph-lite integration, of course, that'd be cheating)
I find the sibling "No declared interfaces - they are defined at the point of use, not declared elsewhere" similarly suspicious, but suspect we'd having a nomenclature mismatch
- 27 open-source tools that can make your Kubernetes workflow easier 🚀🥳
-
Ask HN: Who is hiring? (September 2021)
Kubecost (Stackwatch) | Senior Support Engineer | Remote (US-East/Central preferred) | https://kubecost.com
Our tooling and intelligence empowers teams to efficiently operate Kubernetes at scale—helping them manage cost, performance, and reliability. We're avid contributors to the open source community.
We're looking to add a second Senior Support Engineer to help us build a scalable, user-first support process, troubleshoot complex infrastructure issues, and influence the direction of our product by tracking and communicating user needs. Be one of our first 20 teammates!
Feel free to apply or reach out to us directly with your CV at [email protected] if you're interested!
Check out all of our open roles here: https://angel.co/company/kubecost/jobs
-
Ask HN: Who is hiring? (August 2021)
Kubecost (Stackwatch) | Senior Support Engineer | Remote (US-East/Central preferred) | Full time | https://kubecost.com
Stackwatch is a tight-knit, fast-growing team on the leading edge of cloud infrastructure technology. Starting with our flagship product Kubecost, we build tooling and intelligence that empowers teams to efficiently operate Kubernetes at scale—helping them manage cost, performance, and reliability.
As our second Senior Support Engineer, you’ll help us build a scalable, customer-first support process, troubleshoot complex infrastructure issues for our users, and influence the direction of our product by tracking and communicating customer needs. We’re looking for someone who is as passionate about our product and customers as we are—as one of our first 20 employees, you’ll have the opportunity to shape the future of our support organization and technology.
Feel free to reach out to us directly with your CV at [email protected] if you're interested!
NB: also hiring for Senior Software Engineers and Go-to-market!
-
How to monitor Kubernetes costs with Kubecost and the Lens IDE
Lens is the most powerful IDE for those who need to deal with Kubernetes clusters on a daily basis. It allows you to manage your cluster and view important health metrics. A Kubecost and Lens integration allows you to also visualize Kubernetes costs directly in the Lens UI. With Lens and Kubecost you can view costs and spend efficiency by namespace, pod, deployment and more!
-
What are your killer tips for kubernetes cost optimization?
First you have to be aware of your costs :) This open source project can help https://kubecost.com, `helm install` and get started in 5 minutes
-
How to know the cost impact of your Helm charts install?
Happy to share some of the lessons we've learned if you want to reach out to team [at] kubecost.com. We worked on this problem at Google before launching Kubecost open source.
What are some alternatives?
sig-storage-local-static-provisioner - Static provisioner of local volumes
Gravitational Teleport - The easiest, and most secure way to access and protect all of your infrastructure.
topolvm - Capacity-aware CSI plugin for Kubernetes
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
csi-lib-utils - Common code for Kubernetes CSI sidecar containers (e.g. `external-attacher`, `external-provisioner`, etc.)
kube-burner - Kubernetes performance and scale test orchestration framework written in golang
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
hookdeck-cli - Receive events (e.g. webhooks) in your development environment
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
nakama - Distributed server for social and realtime games and apps.
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.