From 519d5a8b7ad37eccee61d1f290d522801c86c1e7 Mon Sep 17 00:00:00 2001 From: Aaron Crickenberger Date: Fri, 31 Aug 2018 13:33:16 -0700 Subject: [PATCH] Fix scalability charter typos --- sig-scalability/charter.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sig-scalability/charter.md b/sig-scalability/charter.md index acb051d3f12..ace0ed59435 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,