summaryrefslogtreecommitdiff
path: root/sigs.yaml
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2018-12-20 12:45:59 -0800
committerGitHub <noreply@github.com>2018-12-20 12:45:59 -0800
commit1b95dcfb8d073379191382daa883c15e687b2e96 (patch)
treed3f411de14a137519341e9628d8ed28aceb005c0 /sigs.yaml
parenteb468f49f545440e8f64e4c1baedb4597a090138 (diff)
parentd44716b034d44d5908ba081eccc1d6cd75ae89d8 (diff)
Merge pull request #3047 from wojtek-t/update_sig_readme
Update sig scalability readme
Diffstat (limited to 'sigs.yaml')
-rw-r--r--sigs.yaml37
1 files changed, 24 insertions, 13 deletions
diff --git a/sigs.yaml b/sigs.yaml
index cd003124..7b61e319 100644
--- a/sigs.yaml
+++ b/sigs.yaml
@@ -1564,16 +1564,21 @@ sigs:
- name: Scalability
dir: sig-scalability
mission_statement: >
- Responsible for answering scalability related questions such as:
+ SIG Scalability is responsible for defining and driving scalability goals
+ for Kubernetes. We also coordinate and contribute to general system-wide
+ scalability and performance improvements (not falling into the charter of
+ other individual SIGs) by driving large architectural changes and finding
+ bottlenecks, as well as provide guidance and consultations about any
+ scalability and performance related aspects of Kubernetes.
- 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://git.k8s.io/community/sig-scalability/goals.md)
- charter_link:
+ We are actively working on finding and removing various scalability
+ bottlenecks which should lead us towards pushing system's scalability
+ higher. This may include going beyond 5k nodes in the future - although
+ that's not our priority as of now, this is very deeply in our area of
+ interest and we are happy to guide and collaborate on any efforts towards
+ that goal as long as they are not sacrificing on overall Kubernetes
+ architecture (by making it non-maintainable, non-understandable, etc.).
+ charter_link: charter.md
label: scalability
leadership:
chairs:
@@ -1611,13 +1616,19 @@ sigs:
- name: sig-scalability-test-failures
description: Test Failures and Triage
subprojects:
- - name: kubemark
+ - name: kubernetes-scalability-definition
+ owners:
+ - https://github.com/kubernetes/community/blob/master/sig-scalability/slos/OWNERS
+ - name: kubernetes-scalability-governance
+ owners:
+ - https://github.com/kubernetes/community/blob/master/sig-scalability/governance/OWNERS
+ - name: kubernetes-scalability-test-frameworks
owners:
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/cmd/kubemark/OWNERS
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/kubemark/OWNERS
- - name: perf-tests
- owners:
- - https://raw.githubusercontent.com/kubernetes/perf-tests/master/OWNERS
+ - https://raw.githubusercontent.com/kubernetes/kubernetes/master/test/kubemark/OWNERS
+ - https://raw.githubusercontent.com/kubernetes/perf-tests/blob/master/clusterloader2/OWNERS
+ - https://raw.githubusercontent.com/kubernetes/perf-tests/blob/master/OWNERS
- name: Scheduling
dir: sig-scheduling
mission_statement: >