Live data from Hacker News

1000 nodes and beyond: updates to Kubernetes performance and scalability

blog.kubernetes.io

1–10 of 59 posts

Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability

#2
It's exciting to see that Kubernetes is ready for basically any scale. You're more likely to run out of quota (on your cloud provider, particularly IPs) or some other resource (on-prem) before you can't schedule a container quickly enough.

Disclaimer: I work on Compute Engine and chat with the Kubernetes folks a lot.

Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability

#3
1.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.

Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability

#4
post #3

1.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

#5
post #3

1.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.

Running it on AWS is supported, and the team is making strides to make it even better! (Complain loudly via GitHub issues where you find problems).

Cluster Federation (a form of HA) is coming in 1.3.

Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability

#6
post #3

1.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.

kube-aws is a tool that we built at CoreOS to make installation of kubernetes on AWS easier. We just made a new release (v0.5.1) and would love feedback on that. It is what we use in production here at CoreOS. https://github.com/coreos/coreos-kubernetes/releases

Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability

#8
post #7

The 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.

That's the nginx response time. You can see that when he scales up the loadbots but not the backends and says that the "tail latency has gotten quite high" (about 1min in).

Re: 1000 nodes and beyond: updates to Kubernetes performance and scalability

#10

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?

Post reply on HN