I'm in favour of the proposal, Cameron. Building a bridge between Mesos and Kubernetes will be beneficial for both communities. Virtual kubelet effort looks promising indeed and is definitely a worthwhile approach to build the bridge.
While we will need some sort of a scheduler when implementing a provider for mesos, we don't need to implement and use a "default" one: a simple mesos-go based scheduler will be fine for the start. We can of course consider building a default scheduler, but this will significantly increase the size of the project. An exercise we will have to do here is determine which parts of a kubernetes task specification can be "converted" and hence launched on a Mesos cluster. Once we have a working prototype we can start testing and collecting data. Do you want to come up with a plan and maybe a more detailed proposal? Best, Alex
