Brian Grant

There were discussions regarding how compatible it should be with App Engine and with Borg. Docker, buildpacks, and Omlet (a new node agent under development to replace Borglet) were compared. Early discussions presumed a managed service, like GCE, App Engine, and Borg

In September 2013, viewpoints of 9+ WG participants were collected and composed into a "Unified Compute PRD", focused on serving workloads (e.g., rather than batch). That was the first time I was aware of the term "Container as a Service" being used

In October, subgroups of the WG were formed to focus on key problems, including a container management API subgroup. In November, we pulled in more people from Borg and from Cloud to hash out a number of API details. In December, an API proposal was presented to the full WG

That OSS container platform was Project 7. After, there were several proposals from both the Borg side and Cloud side to build products with compatible APIs. Collaboration with the Borg team deepened. Borglet team members started to work on libcontainer for Docker in April 2014

It soon became clear that other Borg team members (me @thockin @erictune4 Dawn Chen @originalavalamp @davidopp @vishnukanan) should work on the open-source project to design and develop the Borg-like functionality. We deeply believed in the potential value to external users

Ah, I found that @jbeda covered some of this background from the Cloud side in his podcast: https://kubernetespodcast.com/episode/012-kubernetes-origins/ …