hajimari VS metallb

Did you take a look at hajimari?

There are a few of these in the wild already. I've personally used https://github.com/toboshii/hajimari successfully. You can have it list services on a landing page dynamically and formatted based on annotations you add to the ingress resource. Works pretty well.

Another one for the list, one that I personally use at home and work:

* hajimari - https://github.com/toboshii/hajimari

Autodiscovery based on Kubernetes Ingress objects is a really nice feature: you configure the details using labels (name, icon etc.) in case the Ingress is not exactly what you want.

Done https://github.com/toboshii/hajimari/issues/20

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.