Comment on Questions regarind k8s ingress
thejml@lemm.ee 5 weeks ago
You’ll want to look into “keepalived” to setup a shared IP across all worker nodes in the cluster and either directly forward, or setup haproxy on each to do the forwarding from that keepalived IP to the ingresses.
I’m running 6 kube nodes (running Talos) running in a 3node proxmox cluster. Both haproxy and keepalived run on the 3 nodes to manage the IP and route traffic to the appropriate backend. Haproxy just allows me to migrate nodes and still have traffic hit an ingress kube node.
Keepalived manages which node is the active node and therefore listens to the IP based on backend communication and a simple local script to catch when nodes can’t serve traffic.
Hercules@lemmy.world 5 weeks ago
Thanks for your response!
I haven’t used keepalived or haproxy before, but i quickly took a look at it. Do you mean i should setup 2 new vms which run keepalived an ha proxy?
While looking at keepalived i remembered reading about (kube-vip)[kube-vip.io]. Couldnt this also help me with the issue? Since this also uses a vip and 1 node gets elected and its able to inform the network which node this is?
thejml@lemm.ee 5 weeks ago
Honestly, that sounds like a keepalived replacement or equivalent. I went with keepalived because I’m also using the IP for the proxmox cluster itself so it had to be outside kube, but the idea is the same. If all you’re using the IP for is kube, go with kube-vip! But let us know how it works!
Hercules@lemmy.world 5 weeks ago
Currently I only will need to use it for k8s so kube-vip will do the job for now.
ikidd@lemmy.world 5 weeks ago
The Wireguard mode is very interesting. Thanks for that link.