From a35ed160b6a1c3214356ca329c9effed0aeb5716 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Przychodze=C5=84?= Date: Tue, 6 Jul 2021 23:30:43 +0200 Subject: Add information for containerd being CRI of choice for SIG Scalability --- sig-scalability/configs-and-limits/provider-configs.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sig-scalability/configs-and-limits/provider-configs.md b/sig-scalability/configs-and-limits/provider-configs.md index ec38e9a0..a7059fd1 100644 --- a/sig-scalability/configs-and-limits/provider-configs.md +++ b/sig-scalability/configs-and-limits/provider-configs.md @@ -75,6 +75,8 @@ proposed * API server configured for load balancing, other components using standard leader election. +* For performance reasons, it is best to use containerd as a container runtimer. + * Etcd is used for two distinct cluster purposes - cluster state and event processing. These have different i/o characteristics. It is important to scalability testing efforts that the iops provided by the servers to etcd be consistent and protected. These leads to two requirements: * Split etcd: Two different etcd clusters for events and cluster state (note: this is currently the GKE production default as well). -- cgit v1.2.3 From 11f2ba86f08a2ffcdbdd101c1fb606923bd5179a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Przychodze=C5=84?= Date: Wed, 7 Jul 2021 00:08:58 +0200 Subject: Update sig-scalability/configs-and-limits/provider-configs.md Co-authored-by: Noah Kantrowitz --- sig-scalability/configs-and-limits/provider-configs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-scalability/configs-and-limits/provider-configs.md b/sig-scalability/configs-and-limits/provider-configs.md index a7059fd1..9931393d 100644 --- a/sig-scalability/configs-and-limits/provider-configs.md +++ b/sig-scalability/configs-and-limits/provider-configs.md @@ -75,7 +75,7 @@ proposed * API server configured for load balancing, other components using standard leader election. -* For performance reasons, it is best to use containerd as a container runtimer. +* For performance reasons, it is best to use containerd as a container runtime. * Etcd is used for two distinct cluster purposes - cluster state and event processing. These have different i/o characteristics. It is important to scalability testing efforts that the iops provided by the servers to etcd be consistent and protected. These leads to two requirements: -- cgit v1.2.3