metallb VS libvirt-k8s-provisioner

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.

Have a closer look at MetallLB.

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.

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/

Then deploy MetalLB https://metallb.universe.tf/

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.

Quoting from their docs:

metalLB to manage bare-metal LoadBalancer services - WIP - Only L2 configuration can be set-up via playbook.

(https://github.com/kubealex/libvirt-k8s-provisioner)

https://github.com/kubealex/libvirt-k8s-provisioner - A nice and easy to use kubernetes provisioner (both single node and HA) made with Ansible and Terraform!

It doesn't have everything out of the box, but keep your eyes on https://github.com/kubealex/libvirt-k8s-provisioner, it is fast growing and will include soon ci/cd tools and registry, plus rook and some other cool stuff.