diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2021-07-06 22:58:43 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-07-06 22:58:43 -0700 |
| commit | 00f432fbbcab4eec0180a7bb213ddbfc473f4675 (patch) | |
| tree | 68dbf9ace1f0373d6d0642d8eadf638e78b5c93a | |
| parent | d3e611fd99daa1581dcd26dd74cde325e0eb000b (diff) | |
| parent | 11f2ba86f08a2ffcdbdd101c1fb606923bd5179a (diff) | |
Merge pull request #5873 from jprzychodzen/containerd
Add information for containerd being CRI of choice for SIG Scalability
| -rw-r--r-- | sig-scalability/configs-and-limits/provider-configs.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/sig-scalability/configs-and-limits/provider-configs.md b/sig-scalability/configs-and-limits/provider-configs.md index ec38e9a0..9931393d 100644 --- a/sig-scalability/configs-and-limits/provider-configs.md +++ b/sig-scalability/configs-and-limits/provider-configs.md @@ -75,6 +75,8 @@ proposed</td> * API server configured for load balancing, other components using standard leader election. +* 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: * Split etcd: Two different etcd clusters for events and cluster state (note: this is currently the GKE production default as well). |