MetalLB Reviews and details

Social recommendations and mentions

• Self hosted kubernetes

  Hey guys, I want to share a guide I’m pretty proud of which is talking about setting up kubernetes which leverages https://kubespray.io/#/ and https://metallb.universe.tf/ so you can host this yourself most people when spinning up kubernetes opt for k3s or get stuck with all the options or unable to setup the external ips for their services so these tools will eliminate the problem. Source: 6 months ago

• Trouble with RKE2 HA Setup: Part 2

  To avoid that, you can use a combination of haproxy and keepalived, an enterprise grade load balancer like the one from F5 or Citrix. Besides that you can also work with https://kube-vip.io or https://metallb.universe.tf. Source: almost 1 year ago

• Kubernetes and feeling defeated

  Not sure if klipper is usable in a cluster with multiple nodes, as it binds to one port only. You may want to use MetalLB instead: https://metallb.universe.tf/. Source: about 1 year ago

• Own kubernetes cluster

  What issue do you see with the load balancer? For self hosted clusters, one can use MetalLB for example to have such single outfacing IP which will failover to another node keeping the same IP if a node dies. Source: about 1 year ago

• PaperLB: A Kubernetes Network Load Balancer Implementation

  Not to take anything away from OP but MetalLB also provides local load balancing. Source: about 1 year ago

• libvirt-k8s-provisioner - Ansible and terraform to build a cluster from scratch in less than 10 minutes ok KVM - Updated for 1.26

  MetalLB to manage bare-metal LoadBalancer services - WIP - Only L2 configuration can be set-up via playbook. Source: about 1 year ago

• 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/. Source: over 1 year ago

• Question: How does Kubernetes know what IPs to use for a NodePort Service

  MetalLB is good for the use case you point out. Source: over 1 year ago

• 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. Source: over 1 year ago

• Is it possible to access the service with <loadbalancer IP>:<nodeport>

  Use an ingress controller and LoadBalancer type as expected, if running on bare metal use something like [MetalLB](https://metallb.universe.tf/) to create a routable IP using DHCP and then use DNS with a hostname pointing to that routable IP for the ingress controller to work. Source: over 1 year ago

• Configuring Ingress on-premise

  In k8s you need a load balancer. In cloud setups, the ingress will create one for you. In bare metal setups you can use something like MetalLB (https://metallb.universe.tf/). Source: almost 2 years ago

• Ask HN: What is your Kubernetes nightmare?

  > Kubernetes on bare metal is actually pretty easy. I would not call it easy at all. Last time I tried that a year ago you still needed a special load balancer to get it going (https://metallb.universe.tf). Has this changed? - Source: Hacker News / almost 2 years ago

• doyouneedkubernetes.com

  K8s was built to run on cloud hosted services, so you would normally use their load balancer. There's two ways that I know of to avoid using a cloud LB. One use metallb or two you can use something like calico to communicate with your networking equipmen through bgp. Source: almost 2 years ago