Kubernetes v.s. Mesos

Evan Lin

Kubernetes Mesos

Architecture Monolithic ( shared state on support of multi scheduler) Two-level

Multiple Scheduler support Yes Ongoing

Priority preemption Yes (1.8) Ongoing

Support multiple Container runtimes

Yes(Rkt, Docker, Clear container(1.7) )

Yes(Mesos, Rkt, Docker)

Suitable for standalone BigData Ongoing (1.8 for spark) Yes

Container Network CNI CNI, CNM

Plugin Network plugin , Device plugin(1.8 alpha).

Built-in support GPU (1.0)

Why big companies choose mesos

• Mesos has well practice in big companies (refer).• Kubernetes not widely use before 1.6 (refer)• Big data best practice orchestration still focus on

SMACK (Spark, Mesos, Akka, Cassandra, Kafka)

Kubernetes getting hot

Refer github 2017/10 report https://octoverse.github.com/

2017/06 Redhat MEC slide

Kubernetes and Mesos Feature Timeline

2016/12 [1.5]

- Daemon Set - Better Federation

2017/01

2017/03 [1.6] - Support over 5000 nodes. - RBAC

2017/02 [1.0] Tensorflow 1.0 support variant machine learning

2017/02 2017/03 2017/06 2017/09

2017/01 2017/02 2017/03 2017/06 2017/09

2016/11 [1.1]

- GPU (1.0) - Windows (1.0)- Health check (1.1)

2017/03 [1.2]

- Container attach- Teardown unregister framework

2017/06 [1.3]

- Multi-Role, Multi-User

2017/09 [1.4]

- Hierarchy-resource (alpha)- More container type

2017/09 [1.8]- Device Plugin- Better RBAC- Native Spark support

2017/06 [1.7]- Stateful Set- Security Improvements- Local Storage