hetzner-k3s
local-path-provisioner
Our great sponsors
hetzner-k3s | local-path-provisioner | |
---|---|---|
45 | 30 | |
1,360 | 1,994 | |
- | 3.3% | |
8.7 | 6.1 | |
8 days ago | 5 days ago | |
Crystal | Go | |
MIT License | 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.
hetzner-k3s
-
New record: I created a 300-node Kubernetes cluster in 11 minutes
This is with the new version not yet released of my tool https://github.com/vitobotta/hetzner-k3s.
It uses k3s as Kubernetes flavor and Hetzner Cloud as provider. For this test I used extremely high concurrency so the tool hung twice of the process because I was hitting the Hetzner API too hard, so I had to interrupt it again and continue.
Excluding the time it paused/hubg due to the API, I calculated around 11 minutes total for the cluster creation. This includes:
- creating all the resources (cloud instances, firewall, load balancer for the Kubernetes API)
-
Best way to deploy K8s to single VPS for dev environment
Try my project Hetzner-K3s, itโs by far the easiest and quickest way to create and manage clusters in Hetzner cloud. https://github.com/vitobotta/hetzner-k3s
-
(For Kubernetes users mainly) I need your help/advice with a business idea
Hi all, if you already use Kubernetes in any capacity or are you interested in it, would you mind spending a few minutes voting in a quick poll and hopefully answering a few questions? I would appreciate your help a ton because it would help me make the right decision and hopefully avoid a costly waste of time.
Everything is in a Github discussion at https://github.com/vitobotta/hetzner-k3s/discussions/296. A huge thank you in advance if you can help with this!
-
V1.1.5 of Hetzner-k3s (my Kubernetes installer for Hetzner Cloud) is out
The new release introduces more customisation options for cluster/service CIDRs, cluster DNS, updated manifests for CSI/CCM/autoscaler, and a couple of improvement for creating large clusters. Check it out at https://github.com/vitobotta/hetzner-k3s
If you are already familiar with this tool, I'd love to know how it's worked for you so far. :)
-
K3s โ Lightweight Kubernetes
https://github.com/vitobotta/hetzner-k3s
Kubernetes on Hetzner Cloud the easiest way
-
K3s on hetzner virtual hosts
Thereโs this cool GitHub project that helps automate a lot of the process for K3s on Hetzner: https://github.com/vitobotta/hetzner-k3s
-
Savings cost for self managed K8s?
If you are willing to leave AWS in order to save a lot of money, you have an option in https://github.com/vitobotta/hetzner-k3s
- hetzner-k3s v.1.1.2 is out with support for the new , powerful but cheap ARM instances! ๐
- hetzner-k3s v1.1.1 is out! ๐
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
What are some alternatives?
k3d - Little helper to run CNCF's k3s in Docker
sig-storage-local-static-provisioner - Static provisioner of local volumes
rke2
topolvm - Capacity-aware CSI plugin for Kubernetes
k-andy - Low cost Kubernetes stack for startups, prototypes, and playgrounds on Hetzner Cloud.
csi-lib-utils - Common code for Kubernetes CSI sidecar containers (e.g. `external-attacher`, `external-provisioner`, etc.)
ansible-role-k3s - Ansible role for deploying k3s cluster
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
k3sup - bootstrap K3s over SSH in < 60s ๐
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
terraform-hcloud-kube-hetzner - Optimized and Maintenance-free Kubernetes on Hetzner Cloud in one command!
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.