From ed074fe196138fdbb04130b07f38af9cd53a4c13 Mon Sep 17 00:00:00 2001 From: Silvio Moioli Date: Thu, 23 May 2024 16:25:17 +0200 Subject: [PATCH] tuning: recommend colocation (#1289) Signed-off-by: Silvio Moioli Co-authored-by: Marty Hernandez Avedon --- .../tuning-and-best-practices-for-rancher-at-scale.md | 8 ++++++++ .../tuning-and-best-practices-for-rancher-at-scale.md | 8 ++++++++ .../tuning-and-best-practices-for-rancher-at-scale.md | 8 ++++++++ .../tuning-and-best-practices-for-rancher-at-scale.md | 8 ++++++++ 4 files changed, 32 insertions(+) diff --git a/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 9242749aa5e..f89282e1870 100644 --- a/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -105,6 +105,14 @@ Although managed Kubernetes services make it easier to deploy and run Kubernetes Use RKE2 for large scale use cases. +### Keep all Upstream Cluster Nodes co-located + +To provide high availability, Kubernetes is designed to run nodes and control components in different zones. However, if nodes and control plane components are located in different zones, network traffic may be slower. + +Traffic between Rancher components and the Kubernetes API is especially sensitive to network latency, as is etcd traffic between nodes. + +To improve performance, run all upstream node clusters in the same location. In particular, make sure that latency between etcd nodes and Rancher is as low as possible. + ### Keeping Kubernetes Versions Up to Date You should keep the local Kubernetes cluster up to date. This will ensure that your cluster has all available performance enhancements and bug fixes. diff --git a/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 9242749aa5e..f89282e1870 100644 --- a/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -105,6 +105,14 @@ Although managed Kubernetes services make it easier to deploy and run Kubernetes Use RKE2 for large scale use cases. +### Keep all Upstream Cluster Nodes co-located + +To provide high availability, Kubernetes is designed to run nodes and control components in different zones. However, if nodes and control plane components are located in different zones, network traffic may be slower. + +Traffic between Rancher components and the Kubernetes API is especially sensitive to network latency, as is etcd traffic between nodes. + +To improve performance, run all upstream node clusters in the same location. In particular, make sure that latency between etcd nodes and Rancher is as low as possible. + ### Keeping Kubernetes Versions Up to Date You should keep the local Kubernetes cluster up to date. This will ensure that your cluster has all available performance enhancements and bug fixes. diff --git a/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 9242749aa5e..f89282e1870 100644 --- a/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -105,6 +105,14 @@ Although managed Kubernetes services make it easier to deploy and run Kubernetes Use RKE2 for large scale use cases. +### Keep all Upstream Cluster Nodes co-located + +To provide high availability, Kubernetes is designed to run nodes and control components in different zones. However, if nodes and control plane components are located in different zones, network traffic may be slower. + +Traffic between Rancher components and the Kubernetes API is especially sensitive to network latency, as is etcd traffic between nodes. + +To improve performance, run all upstream node clusters in the same location. In particular, make sure that latency between etcd nodes and Rancher is as low as possible. + ### Keeping Kubernetes Versions Up to Date You should keep the local Kubernetes cluster up to date. This will ensure that your cluster has all available performance enhancements and bug fixes. diff --git a/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 9242749aa5e..f89282e1870 100644 --- a/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -105,6 +105,14 @@ Although managed Kubernetes services make it easier to deploy and run Kubernetes Use RKE2 for large scale use cases. +### Keep all Upstream Cluster Nodes co-located + +To provide high availability, Kubernetes is designed to run nodes and control components in different zones. However, if nodes and control plane components are located in different zones, network traffic may be slower. + +Traffic between Rancher components and the Kubernetes API is especially sensitive to network latency, as is etcd traffic between nodes. + +To improve performance, run all upstream node clusters in the same location. In particular, make sure that latency between etcd nodes and Rancher is as low as possible. + ### Keeping Kubernetes Versions Up to Date You should keep the local Kubernetes cluster up to date. This will ensure that your cluster has all available performance enhancements and bug fixes.