Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix scalability charter typos #2617

Merged
merged 1 commit into from
Aug 31, 2018
+3 −3
Merged

Fix scalability charter typos #2617

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions sig-scalability/charter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,8 @@ architectural changes.
- Improving performance/scalability of features falling into charters of
individual SIGs.


## What can we do/require from other SIGs

Scalability and performance are horizontal aspects of the system - changes in a
single place of Kubernetes may affect the whole system. As a result, to
effectively ensure Kubernetes scales, we need a special cross-SIG privileges.
Expand All @@ -62,9 +62,9 @@ effectively ensure Kubernetes scales, we need a special cross-SIG privileges.
[performance/scalability SLOs] regression (identified by the set of release
blocking scalability/performance tests). The offending PR should only be
merged again after proving to pass tests at scale.
- In the even of a performance regression, we can block all PRs from being
- In the event of a performance regression, we can block all PRs from being
merged into the relevant repos until the cause of the regression is
identified and mitigated.
identified and mitigated.
The “Rules of engagement” of pausing merge-queue and rationale for
necessity of its introduce are explained in [a separate doc](./block_merges.md).
- We require significant changes (in terms of impact, such as: update of etcd,
Expand Down