No, as long as it's 3.10+ (minimum supported version for DCOS generally) it should be good to go.

1. This is largely a restriction that comes from earlier versions. In earlier versions we relied on the source port to be in the range, as we remapped it in user space. Now, we let iptables / conntrack do it. We might go back to writing it with the conntrack entry though. There are some unfortunate awkward aspects of how iptables does free tulle mapping that can prove annoying.

2. This is a complicated question. You don't pay minuteman for active connections, only at connection construction time. You are reliant on netfilter's conntrack capabilities. By default these are built for 100s of thousands of connections. Given that in DC/OS this runs on every client, we are fairly confident in this approach, though conntrack could reasonably scale to millions of connections.

Stay tuned! It is on our roadmap. If you're interested in the feature, please file a bug on our JIRA: dcosjira.atlassian.net

More likely a reference to the minutemen of the US Revolutionary War, which the ICBM was also named after: https://en.wikipedia.org/wiki/Minutemen

I really enjoy naming things. The naming has a bit of a history. The first version used open flow. We wrote the flows on demand for the connections, and the project's name was 'Minuteman: flows at a moment's notice' as a reference to the soldiers during the revolutionary war that were prepared to fight at a moment's notice.

Although we changed the architecture, we decided to stick with Minuteman. Mesosphere's naming scheme has historically had to do with space. The road to the stars was originally paved by programs such as Minuteman -- Our mission is to orchestrate the data center. You can't do that without networking. Minuteman is our first networking component of many as one of the first components to help pave our way.