community/sig-scalability
Christoph Blecker e0c807ce1c
Regenerate docs
2018-01-24 12:58:19 -08:00
..
slis API-machinery SLIs 2017-08-16 16:29:49 +02:00
slo API-machinery SLIs 2017-08-16 16:29:49 +02:00
slos API-machinery SLIs 2017-08-16 16:29:49 +02:00
OWNERS Add sig labels and use aliases in OWNERS files 2017-10-27 09:34:18 -07:00
README.md Regenerate docs 2018-01-24 12:58:19 -08:00
extending_slo.md Merge pull request #1200 from porridge/grammar-typo-fixes 2017-10-16 15:09:41 -07:00
goals.md Copy piece from the original doc. 2017-10-16 16:40:50 +02:00
provider-configs.md Use git.k8s.io for links 2017-12-21 18:34:08 -08:00
thresholds.md Merge pull request #1078 from warmchang/thresholds 2017-10-24 22:37:49 -07:00

README.md

Scalability SIG

Responsible for answering scalability related questions such as: What size clusters do we think that we should support with Kubernetes in the short to medium term? How performant do we think that the control system should be at scale? What resource overhead should the Kubernetes control system reasonably consume? For more details about our objectives please review our Scaling And Performance Goals

Meetings

Leads

Contact

GitHub Teams

The below teams can be mentioned on issues and PRs in order to get attention from the right people. Note that the links to display team membership will only work if you are a member of the org.

The google groups contain the archive of Github team notifications. Mentioning a team on Github will CC its group. Monitor these for Github activity if you are not a member of the team.

Team Name Details Google Groups Description
@kubernetes/sig-scalability-api-reviews link link API Changes and Reviews
@kubernetes/sig-scalability-bugs link link Bug Triage and Troubleshooting
@kubernetes/sig-scalability-feature-requests link link Feature Requests
@kubernetes/sig-scalability-misc link link General Discussion
@kubernetes/sig-scalability-pr-reviews link link PR Reviews
@kubernetes/sig-scalability-proprosals link link Design Proposals
@kubernetes/sig-scalability-test-failures link link Test Failures and Triage

Remaining 2017 Meeting Dates

  • 10/5
  • 10/19
  • 11/2
  • 11/16
  • 11/30
  • 12/14
  • 12/28 - no meeting

Scalability SLOs

We officially support two different SLOs:

  1. "API-responsiveness": 99% of all API calls return in less than 1s

  2. "Pod startup time: 99% of pods (with pre-pulled images) start within 5s

This should be valid on appropriate hardware up to a 5000 node cluster with 30 pods/node. We eventually want to expand that to 100 pods/node.

For more details how do we measure those, you can look at: http://blog.kubernetes.io/2015_09_01_archive.html

We are working on refining existing SLOs and defining more for other areas of the system.