If you need service discovery, replicas, rolling deploys, etc. ACI probably isn't for you. Check some of the experimental work we released today connecting ACI with Kubernetes: https://github.com/Azure/aci-connector-k8s

Was looking to see if one of you guys turned up in this thread. "And how was the Deis team involved in this?" Didn't see any mention of you all in the article.

Thanks for showing up and weighing in on this! k8s connector looks really cool, is this a totally unique thing or are there anything comparable for ECS? I've never heard of a Kubernetes cluster with virtual nodes! Sounds like you could use this connector and potentially save yourself from ever needing to configure autoscaling in the Kube cluster.

I'm really curious how things are going at Microsoft for this incredibly productive team of people, from Deis, who have put out so much great software that has kept my attention. Hope that everything is great!

ACI lets you schedule individual containers (technically container groups, which are equivalent to K8s pods). Everything on top of that - scaling, service discovery, rolling upgrades, etc. - is up to you. That's why we think the Kubernetes connector [1] is interesting:

[1]: https://github.com/azure/aci-connector-k8s

Wasn't Microsoft heavily invested in Mesos / DCOS?

We have an open source project for this: github.com/hyperhq/hypernetes. Basically use k8s to schedule hypervisor-based secure containers.