diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-08-31 15:52:58 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-08-31 15:52:58 -0700 |
| commit | c155f342d4315313fa13be43d32ce9b7b0930b8c (patch) | |
| tree | b35d72f67bbd1191666463ec6f35671b83aa178f | |
| parent | a3ec48382bf11ed887fb64ff1a08903e7807c861 (diff) | |
| parent | 519d5a8b7ad37eccee61d1f290d522801c86c1e7 (diff) | |
Merge pull request #2617 from spiffxp/sig-scalability-typos
Fix scalability charter typos
| -rw-r--r-- | sig-scalability/charter.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/sig-scalability/charter.md b/sig-scalability/charter.md index acb051d3..ace0ed59 100644 --- a/sig-scalability/charter.md +++ b/sig-scalability/charter.md @@ -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. @@ -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, |