<!---
This is an autogenerated file!

Please do not edit this file directly, but instead make changes to the
sigs.yaml file in the project root.

To understand how this file is generated, see generator/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](https://github.com/kubernetes/community/blob/master/sig-scalability/goals.md)

## Meetings
* [Thursdays at 16:00 UTC](https://zoom.us/j/989573207) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=16:00&tz=UTC).

Meeting notes and Agenda can be found [here](https://docs.google.com/a/bobsplanet.com/document/d/1hEpf25qifVWztaeZPFmjNiJvPo-5JX1z0LSvvVY5G2g/edit?usp=drive_web).

## Leads
* [Daniel Smith](https://github.com/lavalamp), Google
* [Bob Wise](https://github.com/countspongebob), Samsung SDS
* [Joe Beda](https://github.com/jbeda), Heptio

## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-scalability)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-scale)

<!-- BEGIN CUSTOM CONTENT -->
## Scalability SLOs

We officially support two different SLOs:

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

1. "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.
<!-- END CUSTOM CONTENT -->
