kuard VS metallb

I would recommend setting up a simple Kubernetes cluster (maybe using KinD, minikube, or something similar) and getting to know how it works (you could try deploying something like Kuard or Podinfo or deploy one of your own containerized apps to Kubernetes).

https://github.com/kubernetes-up-and-running/kuard?

theres also https://github.com/kubernetes-up-and-running/kuard which gives you the option of allocating more memory at runtime

Kubernetes up and running is also a basic example App you can deploy and play around with

Ive used this previously when demoing k8s stuff https://github.com/kubernetes-up-and-running/kuard

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.