1000 nodes and beyond: updates to Kubernetes performance and scalability

Re:1000 nodes and beyond: updates to Kubernetes performance ... by jbeda on Monday March 28, 2016 @04:46PM (#11377257)

Funny story -- Google Container Engine was the obvious name for that product but the TLA for it (GCE) conflicted with Google Compute Engine. We broke the tie by deciding the TLA for Container Engine would be GKE. The 'K' is a nod toward the Kubernetes underpinnings.

Google Compute Engine itself was difficult to name. There were those that were pushing for Google Compute Cluster. But I veto'd as the TLA would have been GCC or GC2. Both would have been awful.

Naming is hard.

[ Parent | on HN ]

Re:1000 nodes and beyond: updates to Kubernetes performance ... by AndrewWright on Monday March 28, 2016 @05:38PM (#11377626)

Why not go with Alphabet Cloud, or ABC?

[ Parent | on HN ]

Re:1000 nodes and beyond: updates to Kubernetes performance ... by thesandlord on Monday March 28, 2016 @05:56PM (#11377728)

Hahaha this is awesome! Unfortunately, Alphabet wasn't a thing back then.

[ Parent | on HN ]

Re:1000 nodes and beyond: updates to Kubernetes performance ... by stretchwithme on Monday March 28, 2016 @04:57PM (#11377344)

Maybe abbreviations could be more flexible with G always having to be the first letter.

[ Parent | on HN ]

Re:1000 nodes and beyond: updates to Kubernetes performance ... by jbeda on Monday March 28, 2016 @05:04PM (#11377389)

It gets a lot harder to name things world wide if you don't start with "Google". gmail in Germany was a lesson: http://techcrunch.com/2012/04/14/google-finally-gets-right-t...

[ Parent | on HN ]

Re:1000 nodes and beyond: updates to Kubernetes performance ... by stretchwithme on Monday March 28, 2016 @05:18PM (#11377478)

Is gmail an acronym?

[ Parent | on HN ]