longhorn
metallb
Our great sponsors
longhorn | metallb | |
---|---|---|
59 | 67 | |
4,404 | 5,493 | |
2.4% | 1.2% | |
8.3 | 9.5 | |
4 days ago | 7 days ago | |
Shell | 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.
longhorn
-
Just finished migrating my old tower servers to a Kubernetes cluster on my new rack!
For my primary CSI provider, I use Longhorn, and to administrate my clusters, I use the Kubernetes Dashboard. In front of all of my private dashboards, I use Traefik Forward Auth to limit who can access them.
-
NAS on a cluster
Maybe with https://longhorn.io
-
TopoLVM to provide local storage
For data must be protected, I use Longhorn https://longhorn.io/ which is basically iSCSI/NFS with replication.
-
Homelab and Long Term Data Integrity?
Backups are definitely necessary. The problem though is that you cant detect by default if you are backing up corrupted data. By now i found three approaches: 1. Use a filesystem that detects and fixes errors (e. g. btrfs or zfs) 2. Use par2 (parchive) to generate checksums on your files manually 3. I found the following issue on the k8s storage solution I currently use: https://github.com/longhorn/longhorn/issues/3198 For now I am waiting for option 3 getting merged. In the long run I will upgrade my laptop to btrfs and for now use par2. Hope that provides a starting point. Feel free to add your ideas!
-
Change SSH port
You can use the Longhorn iSCSI installer script as an example. https://github.com/longhorn/longhorn/blob/master/deploy/prerequisite/longhorn-iscsi-installation.yaml
-
Learning with K3s at home. "Best" storage option for a single-node cluster?
Rancher's Longhorn (even though it's only a single-node)
-
Running Kubernetes cluster locally to self host a bunch of applications along with a DNS server
Application storage now: yes, NAS is probably the best way to go about it. I believe k3s uses some kind of "local storage" by default but there's plenty of alternative Container Storage Interfaces (CSI) out there. Longhorn worked well for me and it covers most uses cases I care about: snapshots, backups, and replication. I don't know about any "NAS providers" though, and once again there will be performance drawbacks with having your storage that externalized.
-
Advice on system design best practices?
For me longhorn works really well as my storage backend.
-
Install and configure a high available Kubernetes cluster with Ansible
Longhorn is a lightweight, reliable, and powerful distributed block storage system for Kubernetes.
-
What selfhosted packages are you using?
You mentioned storage... That's always tricky but provisioning persistent volumes with https://longhorn.io is really simple... It's also easy to setup, the helm chart is wonderful
metallb
-
Créer des applications directement dans Kubernetes avec Acorn …
MetalLB
- Loadbalancer is always pending
-
How hard is it to deploy kubernetes on bare metal in 2022 ?
Set up MetalLB https://metallb.universe.tf/ either via helm or simple manifest. Pick a range of ips to allocate, and assign via manifest https://metallb.universe.tf/configuration/
- Kubernetes e netstat
- K3s with multiple external IPs per node?
-
libvirt-k8s-provisioner - Ansible and terraform to build a cluster from scratch in less than 10 minutes ok KVM - Updated for 1.25
metalLB to manage bare-metal LoadBalancer services - WIP - Only L2 configuration can be set-up via playbook.
-
Back to basics: accessing Kubernetes pods
-- MetalLB
-
What is the 'kubectl run' equivalent of this 'docker run' command?
Heads up: breaking changes in 0.13.2
I gave it a quick try with the snippet bellow and their sample configMap in https://github.com/metallb/metallb/tree/main/configmaptocrs and it does not work. Would've been nice, if the additional configMap definition would be optional. But well..
-
Single node k3s with MetalLB, problems with external IP.
You might want to try a IPAddressPool and a L2Advertisement. The configMap has been deprecated with MetaLB 0.13 (see https://github.com/metallb/metallb/issues/1473 - you'll find my name there in the discussion and PRs as well)
What are some alternatives?
kube-vip - Kubernetes Control Plane Virtual IP and Load-Balancer
rook - Storage Orchestration for Kubernetes
calico - Cloud native networking and network security
ingress-nginx - Ingress-NGINX Controller for Kubernetes
nfs-subdir-external-provisioner - Dynamic sub-dir volume provisioner on a remote NFS server.
zfs-localpv - CSI Driver for dynamic provisioning of Persistent Local Volumes for Kubernetes using ZFS.
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
cert-manager - Automatically provision and manage TLS certificates in Kubernetes
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
kube-plex - Scalable Plex Media Server on Kubernetes -- dispatch transcode jobs as pods on your cluster!
rancher - Complete container management platform
k3s - Lightweight Kubernetes