Hi,
If we’re deploying in docker, is the expectation that we should have a separate container for the tsa-daemon? Looking at the traffic shaping docs they seem to suggest the daemon will be started if configured but that doesn’t seem to be the case when using the docker image.
Also is there a suggested architecture for a two node cluster (both docker hosts)? We realise two nodes wouldn’t allow a quorum but it’s what we’re working with right now.
Thanks.
Deployment Architecture - KumoMTA Docs discusses some strategies for multi-node deployments.
kumomta/examples/docker-swarm at main · KumoCorp/kumomta · GitHub has an example of a multi-instance setup in docker (using docker swarm, but the concepts apply generally)
Note that there is no explicit synchronization between TSA daemons. The same log traffic is sent to all TSA nodes by the MTA nodes so that they all will arrive at the same understanding of the configuration state through eventual consistency.
Thanks for the links Wez. The swarm one makes it all click into place.