Score:0

Set up a single ip for egress / ingress traffic on a docker swarm

ug flag

I have a docker swarm with 3 vms:

  • node1: 192.168.10.1
  • node2: 192.168.10.2
  • node3: 192.168.10.3

Is it possible to have an ip 192.168.10.4 for both ingress and egress traffic.

I know one way of doing the ingress part is with keepalived.

A.B avatar
cl flag
A.B
Afaik, Docker swarm doesn't provide such feature and that's why you get no answer to this question. Some CNI in Kubernetes provide such feature but even there it's uncommon. Example for an open-source one that is not production ready: https://github.com/nirmata/kube-static-egress-ip#how-it-works . You'd probably have to implement somehow something similar in Docker (which uses "CNM" rather than "CNI" ).
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.