Nomad + Consul as a simple orchestrator?

Question

Docker

Good evening :).

It is planned to have 3 combat servers + 3 replicas of these combat servers in another data center. All servers are currently isolated from each other. Each will run nginx+php+mysql with separate projects. Everything, of course, is in the docker, because for me it is already much simpler. Now there is a prototype of this scheme, it works through docker-compose, but we need to move and think about how to do it better.

I have one nomad + consul cluster and I thought to pull this scheme here as well, in order to simply upload the containers I need to the combat and backup servers and it’s easier to control this whole process (besides, then maybe one project will grow and will be not only on the same server). But there is absolutely no desire to trick a cluster of 3 master servers of nomad servers. I would like to make 1 master at the beginning and he sends tasks to all. But there are a couple of things here. What if my master died (the master will be on a virtual machine and I will return everything from backups pretty quickly)? Will already running containers continue to run on clients? And in general, is the skin worth the candle? :).
It would be possible to raise a full-fledged cluster, of course, but is it necessary if everything works well anyway? And minus the Master from each server, I will have an encrypted tunnel and all interaction will go through this tunnel, but if there are several masters, then you won’t have enough tunnels here, you will have to drive traffic through the external one, not quite securely :)

Well, logically, it’s not entirely clear how it is divide everything ...

Or, well, leave it dockercompos and don’t worry? :)

Answer 1

Pick up the cubes and don't worry.