kube-mesos-framework

>> Kubernetes was supposed to be scheduler for Mesos and Google invested in it. > I never heard of such plan. Oh, there was a plan: https://github.com/kubernetes-retired/kube-mesos-framework But it wasn't really in anyone's business model interests, even if it may have made sense for customers and the community.

"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 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 sch

Kubernetes running on DCOS is mentioned, but not treated as a real alternative. Kubernetes can run as an app on top of Mesos the same way marathon can. Note: I am a heavy user of Kubernetes, but not Mesos, so I can't comment how well it works. Kubernetes uses "two phase scheduling" and Mesos can be plugged as a second phase (e.g. https://github.com/kubernetes-incubator/kube-mesos-framework... seems decent). For me it seems like a perfect combination - on the cloud you utilize cool stuff like GKE or https://azure.microsoft.com/en-us/blog/announcing-azure-cont... for phase 2 of schedule, but if your client wants to run your code to run on their servers you can run it on their mesos/dcos deployment.