"I don't think k8s operates as a Meoss framework" Have you ever used Mesos? It is the only way k8s could run ontop of Mesos. Also: https://github.com/kubernet

"I don't think k8s operates as a Meoss framework" Have you ever used Mesos? It is the only way k8s could run ontop of Mesos. Also: https://github.com/kubernetes-incubator/kube-mesos-framework https://github.com/kubernetes-incubator/kube-mesos-framework Also, you could maybe compare Marathon to Kubernetes Dashboard + the Kubernetes apiserver maybe, but comparing the two directly is not remotely close. With Mesos + Marathon, you still need a load balancer for both North <---> South AND East <---> West cluster traffice. This is builtin to Kubernetes via Service and Ingress objects and their associated controllers. There is also Federation, and so much more. Mesos is just a resource scheduler, and a very good two level one at that, built to prove the theory of two level schedulers working well with interactive and batch workloads concurrently. Kubernetes is the entire package and includes a default scheduler, but allows you to plug in your own. Disclaimer: I spent a full year working on Mesos and went to MesosCon twice. After speaking in person with Kelsey Hightower at Monitorama, he convinced me to switch to Kubernetes on purely technical reasons. The stuff that you have to DIY on Mesos is built sensibly and pluggably in Kubernetes. From a cluster operator standpoint frankly, Kubernetes is leagues ahead. Lots of fortune 500s and enterprise customers find the lack if sensible RBAC and real to the core auditing support in Mesos to be seriously lacking. https://twitter.com/nirajtolia/status/903437346443378688 https://twitter.com/nirajtolia/status/903437346443378688