revision of hardware/scale requirements and best practices: port changes to 2.7 and 2.6

Signed-off-by: Silvio Moioli <silvio@moioli.net>
2026-09-25 20:48:11 +00:00 · 2023-10-10 13:33:04 +02:00
parent 01dc68f1cb
commit 28b9fae3f1
4 changed files with 10 additions and 10 deletions
@@ -57,7 +57,7 @@ If you are installing Rancher on a K3s cluster with Alpine Linux, follow [these

 ### RKE Specific Requirements

-For the container runtime, RKE should work with any modern Docker version.
+RKE requires a Docker container runtime. Supported Docker versions are specified in the [Support Matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) page.

 For more information, see [Installing Docker](../getting-started/installation-and-upgrade/installation-requirements/install-docker.md).

@@ -77,13 +77,13 @@ Rancher's hardware footprint depends on a number of factors, including:
 Since there are a high number of influencing factors that may vary over time, the requirements listed here should be understood as reasonable starting points that work well for most use cases. Nevertheless, your use case may have different requirements. For inquiries about a specific scenario please [contact Rancher](https://rancher.com/contact/) for further guidance.

 In particular, requirements on this page are subject to typical use assumptions, which include:
- - Under 60 thousand total Kubernetes resources, per type.
+ - Under 60,000 total Kubernetes resources, per type.
 - Up to 120 pods per node.
 - Up to 200 CRDs in the upstream (local) cluster.
 - Up to 100 CRDs in downstream clusters.
 - Up to 50 Fleet deployments.

-Higher numbers are possible but requirements might be higher. If you have more than 20 thousand resources of the same type, loading time of the whole list through the Rancher UI might take several seconds.
+Higher numbers are possible but requirements might be higher. If you have more than 20,000 resources of the same type, loading time of the whole list through the Rancher UI might take several seconds.

 :::note Evolution:

@@ -7,7 +7,7 @@ title: Tuning and Best Practices for Rancher at Scale
 </head>


-This guide describes the best practices and tuning approaches to scale Rancher setups, and the associated challenges with doing so. As systems grow performance will naturally reduce, but there are steps that can minimize the load put on Rancher, and optimize Rancher's ability to manage larger infrastructures.
+This guide describes the best practices and tuning approaches to scale Rancher setups and the associated challenges with doing so. As systems grow, performance will naturally reduce, but there are steps that can minimize the load put on Rancher and optimize Rancher's ability to manage larger infrastructures.

 ## Optimizing Rancher Performance

@@ -23,7 +23,7 @@ When scaling up Rancher, one typical bottleneck is resource growth in the upstre

 ### Managing Your Object Counts

-Etcd is the backing database for Kubernetes and for Rancher. The database may eventually encounter limitations to the number of a single Kubernetes resource type it can store. Exact limits vary and depend on a number of factors. However, experience indicates that performance issues frequently arise once a single resource type's object count exceeds 60 thousand. Often that type is `RoleBinding`.
+Etcd is the backing database for Kubernetes and for Rancher. The database may eventually encounter limitations to the number of a single Kubernetes resource type it can store. Exact limits vary and depend on a number of factors. However, experience indicates that performance issues frequently arise once a single resource type's object count exceeds 60,000. Often that type is `RoleBinding`.

 This is typical in Rancher, as many operations create new `RoleBinding` objects in the upstream cluster as a side effect.