this post was submitted on 17 Nov 2023
0 points (50.0% liked)

Self-Hosted Main

515 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
 

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?

top 2 comments
sorted by: hot top controversial new old
[โ€“] nerdyviking88@alien.top 0 points 11 months ago (1 children)

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.top 1 points 11 months 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!