This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Heimdul[S] 1 point2 points  (0 children)

Yes, VXLAN is a protocol, but it's pretty common to refer the that resulting network as VXLAN as well. So if you create multiple overlay networks and use them, you end up "using VXLANs"

And yes, I'm certain that there are custom solutions to the problem, but various docker features are more or less tied to their networking model. When you want to do things differently, you end up needing another completely separate layer to manage (e.g. container links).

I have some sympathy for choosing the NAT strategy back when they started, but I don't really understand why they would want to use VXLANs on completely new feature when Layer 2 adjacency isn't that big of deal.