chrisgaun

While Mesos always supported a number of container orchestration layers (e.g. Netflix's Titus), you are right in that Marathon used to be the only container orchestrator for DC/OS up until 2017. Mesosphere DC/OS has had a Kubernetes package in GA since March and we've had 6 releases since then to make sure always was newest version of Kubernetes and to add features (Strict Mode).

Disclaimer: I am the PM at Mesosphere.

Mesos means "middle" and it was designed to handle the declarative infrastructure provisioning for different schedulers... container orchestration schedulers: Aurora (Youtube/Twitter), Titus (Netflix), Marathon and Kubernetes (DC/OS).... analytics schedulers: Spark, Tensorflow, etc.

The idea was always that you should manage this infrastructure just like they are managing containers.

discloser: I am the PM of Kubernetes on DC/OS.

As a discloser, I work at Mesosphere who engineers DC/OS.

I would like to note that DC/OS now has Kubernetes [Beta]. You can manage Kubernetes resources on your DC/OS cluster now.

Here are the instructions on Github to get started: https://github.com/mesosphere/dcos-kubernetes-quickstart You can also join the Slack to help you on you out: http://chat.dcos.io/ (the #kubernetes channel)

DotNETes (Windows container and Hyper-v container) support is here! Disclosure: I worked on DotNETes

DotNETes (Windows container and Hyper-v container) support is here!

Disclosure: I worked on DotNETes

Great news! Azure is really leading AWS in the public container orchestration space.

Thanks for the feedback. We will shoot videos to demo new capabilities as well.

Great to see this much needed update after seeing the team work on it. Anyone interested in contributing to the UI or giving feedback should join the Kubernetes UI SIG https://github.com/kubernetes/community/blob/master/sig-ui/R...

The momentum and features are really unmatched compared to any comparable solution.

Disclosure: I do not work at Google