From c9373b53367f489c04329973fcb4fdec672957e6 Mon Sep 17 00:00:00 2001 From: Marcin Owsiany Date: Mon, 16 Oct 2017 16:01:15 +0200 Subject: [PATCH] Expand AZ acronym. This is a little cryptic to someone with no AWS experience. --- sig-scalability/provider-configs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-scalability/provider-configs.md b/sig-scalability/provider-configs.md index d35dc4527..c960ad22a 100644 --- a/sig-scalability/provider-configs.md +++ b/sig-scalability/provider-configs.md @@ -122,7 +122,7 @@ proposed * Improving the cluster performance loading to match production deployment scenarios is critical on-going work, especially clusterloader: [https://github.com/kubernetes/perf-tests/tree/master/clusterloader](https://github.com/kubernetes/perf-tests/tree/master/clusterloader) -* Multi-zone / multi-az deployments are often used to manage large clusters, but for testing/scalability efforts the target is intentionally a single AZ. This keeps greater consistency between environments that do and don’t support AZ-based deployments. Failures during scalability testing are outside the SIG charter. Protecting against network partitioning and improving total cluster availability (one of the key benefits to a multi-AZ strategy) are currently out scope for the Scalability SIG efforts. +* Multi-zone / multi-az deployments are often used to manage large clusters, but for testing/scalability efforts the target is intentionally a single Availability Zone. This keeps greater consistency between environments that do and don’t support AZ-based deployments. Failures during scalability testing are outside the SIG charter. Protecting against network partitioning and improving total cluster availability (one of the key benefits to a multi-AZ strategy) are currently out scope for the Scalability SIG efforts. * Scalability issues on very large clusters of actual nodes (instead of kubemark simulations) are real. Efforts to improve large cluster networking performance e.g. IPVS are important, and will be interesting areas for cross-SIG collaboration.