So, just for the sake of it I’ve been trying to get my lab to be HA -or as HA as a small homelab can be-

My current set up is a follows:

3 proxmox servers with some Debian VMs, the VMs run docker swarm

A NAS, with Truenas

ISProuter -> OpenWRTRouter -> VM [Port fowards 80/443]

This works like a charm when I am in my LAN, but when I access from outside, if the VM that has 80/443 port forwarded to is down (which it never is) I’d loose connectivity.

I have now idea how to solve this little problem in a efficient way, maybe a reverse proxy running on my OpenWRT? (Which’d only move the point of failure to my router, but if my router goes down is gameover already anyways) has anyone attempted this?

Any opinions/ideas?

Update:

Solved! I moved my traefik data to a NFS share in my NAS, replicated the container across all manager nodes and then installed keepalived and now float a VIP between them.

Works like a charm and it was super easy to set up, literally 3 ansible tasks and 1 jinja template and you are done.

Thanks to all of ya!

  • markstos@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 days ago

    To explain how HAproxy and competing tools solve this:

    Two servers are prepared to be the single reverse proxy, but one is active. They constantly communicate with a “heartbeat”. When the active one fails to send a heartbeat, the secondary executes the steps to become the active primary. When the primary’s heart starts beating again, it becomes active again.

    So there can be a few seconds of downtime, but the failover is automatic.