Does anyone have a good experience to share with a hosted Kubernetes provider outside of GCE and Tectonic? I am primarily comparing using Kubernetes to alternatives such as Rancher or Nomad.
Disclaimer: I work at Google on Kubernetes. Do you mean GKE?
1000 nodes and beyond: updates to Kubernetes performance and scalability
11–20 of 59 posts
Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability
#12Earlier quoted context omitted.
Disclaimer: I work at Google on Kubernetes. Do you mean GKE?
My 'GCE' reference was to Google Container Engine with Kubernetes as the cluster manager, yes.
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.
Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability
#13Earlier quoted context omitted.
My 'GCE' reference was to Google Container Engine with Kubernetes as the cluster manager, yes.
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 bee…
Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability
#14Earlier quoted context omitted.
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 bee…
Maybe abbreviations could be more flexible with G always having to be the first letter.
Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability
#151.2 has a lot of really nice additions such as infrastructure containers, the new config map API, service draining for node replacements, and many more. Unfortunately I would be running it on AWS and HA still hasn't been worked out and manual setup is a bear.
The community is working on what we like to call "self-hosted" Kubernetes. This will help reduce the complexity of installation on all platforms. You can see more about it from my KubeCon keynote: https://youtu.be/A49xXiKZNTQ?t=6m The target is to have this all upstream in the next (v1.3) release. Slides here: https://speakerdeck.com/philips/pushing-kubernetes-forward?s...
Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability
#16The frame at 2:37 shows avg response time of 1.75 ms at 10 mln QPS. Which API call was measured? I'm looking at bar charts under "Metrics from Kubernetes 1.2" and the latencies graphed there appear to be different/higher.
The latency referred to in the demo is the latency of requests from the loadbots to the nginx containers running in the cluster.
Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability
#17Earlier quoted context omitted.
The community is working on what we like to call "self-hosted" Kubernetes. This will help reduce the complexity of installation on all platforms. You can see more about it from my KubeCon keynote: https://youtu.be/A49xXiKZNTQ?t=6m The target is to have this all upstream in the next (v1.3) release. Slides here: https://speakerdeck.com/philips/pushing-kubernetes-forward?s...
FYI, the SlideShare link in that video's description is truncated. I think it's supposed to go here: http://www.slideshare.net/kubecon/kubecon-eu-2016-keynote-pu...
Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability
#18Earlier quoted context omitted.
FYI, the SlideShare link in that video's description is truncated. I think it's supposed to go here: http://www.slideshare.net/kubecon/kubecon-eu-2016-keynote-pu...
The original URL is here: https://speakerdeck.com/philips/pushing-kubernetes-forward
Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability
#19Earlier quoted context omitted.
Maybe abbreviations could be more flexible with G always having to be the first letter.
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...
Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability
#20Disclaimer: I co-founded Kubernetes and help to coordinate the k8s Scalability SIG, although I'm no longer at Google. I didn't see this before it was published, though.