Hi all…

So I’ve moved to Docker Swarm to test it in comparison to K3s. I’m not a huge fan of the complexity of K3s, so I thought I’d give Docker Swarm a shot.

The only issue I have so far is this…

I have 3 manager nodes and 3 worker nodes. However, I have my DNS server pointing the hosted services to the one manager node that hosts NGINX for reverse proxy. My problem is, when one of the manager nodes goes down, the next one takes over, but all the services are still pointing to the first manager node’s IP for NGINX.

NGINX does move to the other manager, but without DNS pointing to the right IP, it’s useless. I really don’t want to have to go change the IP in my DNS server anytime this happens and that defeats the purpose of multiple managers to create HA.

So, what am I doing wrong here?

  • nerdyviking88@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    The solution around this is 2 fold:

    Either use a front end load balancer that sends to the swarm nodes OR Configure the swarm nodes with like KeepaliveD to have a virtual IP address, and then point your DNS to that.

    I’m personally using the second one for the past 4 years very happily.

    • biswb@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      This. This is exactly what I do. And it for both my lab which is my side hustle, and my big boy job. Its perfect!