brendandburns

Kubernetes handles most of this seemlessly for the cluster infrastructure.

The central master handles node failures by removing nodes that aren't heartbeating.

On the node, we require a process monitor for the kubelet (by default we use supervisord) but then the kubelet monitors Docker [and also does garbage collection and resource limiting ], and then all of the other node daemons (e.g. the kubernetes proxy) are run/monitored/restarted by the kubelet.

this was originally sent out on twitter by a bunch of people (including myself) who are working on containers (and have a container-oriented set of followers) so I'm pretty certain there is a forward looking bias in the data.

I tried to describe this bias at the top of the blog post.

Disclaimer: I work on Kubernetes for Google

Its great to see this launch. We've had flexible resources for container workloads for a while, its great to see them be available for more traditional VM workloads too!