Other comments saying k8s (short f/kubernetes) people are in various companies are correct, but adding it was started at Google (and that's where jessfraz works

Other comments saying k8s (short f/kubernetes) people are in various companies are correct, but adding it was started at Google (and that's where jessfraz works on it). Background for k8s is that Google had (has) an internal container scheduler called Borg (https://research.google.com/pubs/pub43438.html https://research.google.com/pubs/pub43438.html) with which they do clever things like pack a CPU-hungry and RAM-hungry process on the same box so all of that machine's resources get used, and can use the same server for a mix of production processes (that might e.g. be latency-sensitive need a dedicated core) and non-production tasks like internal data crunching. For example, a non-production task can run opportunistically when a prod job isn't using its full allocation of RAM, and be preempted if the production tasks need that RAM later or more important tasks come along. Kubernetes is a ground-up effort to do the same sort of thing in the open. The components are different--etcd instead of Chubby, and of course not using Google's internal container stuff for tasks--but idea's the same.