public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-24 20:18:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

installation-requirements: make typical use assumptions more concise

Browse Source 
Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>
This commit is contained in:
Silvio Moioli
2023-10-03 10:32:39 +02:00
committed by GitHub
co-authored by Marty Hernandez Avedon
parent d37a50c041
commit e57f628811
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pages-for-subheaders/installation-requirements.md
+7 -7
View File
@@ -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 higher or lower requirements. For enquiries 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:
- total count of Kubernetes resources under 60 thousand 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.
Note that visualization in the UI might be impacted for users with visibility on all resources in a type above 20 thousand total items.
- Under 60 thousand 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, you might not be able to see all resources through the Rancher UI.
:::note Evolution: