Kubernetes and CoreOS looks like a pretty good strategy for deploying in a cloud env. I'd be interested to see how this might work with the Fleet strategy that is part of CoreOS.
fleet is a cluster-level init system with just enough of a scheduler to handle the fault tolerance of higher-level components (i.e. log aggregation, scheduling, etc). In this case, Kubernetes can be thought of as an application-specific scheduler, as it nontrivially places containers in a cluster. Kubernetes can schedule its containers through fleet's APIs and trust fleet to track the overall state of the cluster.
Would that be valuable though? As described now, it appears that kubernetes just replaced fleet, and seems to do work well. What would be arguments to keep fleet under the hood?