Yes, I know. But large swaths of swarm functionality live in tooling maintained by Docker Inc., and Docker employees seem to work on bits of code related to Swa

Yes, I know. But large swaths of swarm functionality live in tooling maintained by Docker Inc., and Docker employees seem to work on bits of code related to Swarm - sometimes. The separation between those entities is completely opaque. If Swarm is a Mirantis product, why does the Docker CLI, maintained by Docker on GitHub, contain code of that product? Who, if not the maintainers of these projects, should be contacted about that code? Edit: Additionally, if anyone reads this, I actually spoke to Mirantis a while ago. Unless you're ready to pay five to six figures per year for a support contract, there's nothing they can do to alleviate your problems. If Swarm mode would be deprecated ripped out of the Docker CLI and daemon, moved to a separate project under clear ownership of Mirantis and without any pretense of being "open source" software, it would be a different situation. But the way it is, nobody knows or understands what is happening, and Swarm mode crashes into the wall in slow motion.