diff --git a/docs/pages-for-subheaders/installation-requirements.md b/docs/pages-for-subheaders/installation-requirements.md
index 4eb138d46ab..a20374c46eb 100644
--- a/docs/pages-for-subheaders/installation-requirements.md
+++ b/docs/pages-for-subheaders/installation-requirements.md
@@ -108,7 +108,7 @@ Please note that a highly available setup with at least 3 nodes is required for
| Large (*) | Up to 500 | Up to 5000 | 16 | 64 GB |
| Larger (†) | (†) | (†) | (†) | (†) |
-(*): Large deployments require [additional tuning and following of best practices](../reference-guides/best-practices/rancher-server/tips-for-scaling-rancher.md).
+(*): Large deployments require [additional tuning and following of best practices](../reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md).
(†): Depending on various factors, larger deployment sizes are generally possible with ad-hoc hardware recommendations and tuning. You can [contact Rancher](https://rancher.com/contact/) for a customized evaluation.
@@ -126,7 +126,7 @@ Please note that a highly available setup with at least 3 nodes is required for
| Medium | Up to 300 | Up to 3000 | 8 | 32 GB | 4 vCPUs, 16 GB + 2000 IOPS |
| Large (*) | Up to 500 | Up to 5000 | 16 | 64 GB | 8 vCPUs, 32 GB + 4000 IOPS |
-(*): Large deployments require [additional tuning and following of best practices](../reference-guides/best-practices/rancher-server/tips-for-scaling-rancher.md).
+(*): Large deployments require [additional tuning and following of best practices](../reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md).
(†): External Database Host refers to the optional possibility of hosting [k3s cluster data store on an external dedicated host](https://docs.k3s.io/datastore). Exact requirements will depend on the chosen data store, this table is a guideline only.
@@ -146,7 +146,7 @@ These requirements apply hosted Kubernetes clusters such as EKS, AKS, or GKE. Th
| Medium | Up to 300 | Up to 3000 | 8 | 32 GB |
| Large (*) | Up to 500 | Up to 5000 | 16 | 64 GB |
-(*): Large deployments require [additional tuning and following of best practices](../reference-guides/best-practices/rancher-server/tips-for-scaling-rancher.md).
+(*): Large deployments require [additional tuning and following of best practices](../reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md).
### RKE
@@ -160,7 +160,7 @@ Please note that a highly available setup with at least 3 nodes is required for
| Medium | Up to 300 | Up to 3000 | 8 | 32 GB |
| Large (*) | Up to 500 | Up to 5000 | 16 | 64 GB |
-(*): Large deployments require [additional tuning and following of best practices](../reference-guides/best-practices/rancher-server/tips-for-scaling-rancher.md).
+(*): Large deployments require [additional tuning and following of best practices](../reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md).
Refer to RKE documentation for more detailed information on [RKE general requirements](https://rke.docs.rancher.com/os).
diff --git a/docs/reference-guides/best-practices/rancher-server/tips-for-scaling-rancher.md b/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md
similarity index 96%
rename from docs/reference-guides/best-practices/rancher-server/tips-for-scaling-rancher.md
rename to docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md
index cc867ffaa0a..6d35c512935 100644
--- a/docs/reference-guides/best-practices/rancher-server/tips-for-scaling-rancher.md
+++ b/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md
@@ -1,11 +1,13 @@
---
-title: Tips for Scaling Rancher
+title: Tuning and Best Practices for Rancher at Scale
---
-
+
+:docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md
+
This guide aims to introduce the approaches that should be considered to scale Rancher setups, and associated challenges with doing so. As systems grow performance will naturally reduce, but there are steps we can take to minimize the load put on Rancher, as well as optimize Rancher's ability to handle these larger setups.
## General Tips on Optimizing Rancher's Performance
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 3ab17e54bc1..7789a046093 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -1166,6 +1166,10 @@ module.exports = {
{
to: "/v2.7/reference-guides/rancher-security/hardening-guides/rke2-hardening-guide/rke2-self-assessment-guide-with-cis-v1.7-k8s-v1.25",
from: "/v2.7/reference-guides/rancher-security/hardening-guides/rke2-hardening-guide/rke2-self-assessment-guide-with-cis-v1.23-k8s-v1.25"
+ },
+ {
+ to: "/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale",
+ from: "/reference-guides/best-practices/rancher-server/tips-for-scaling-rancher"
}
],
},
diff --git a/sidebars.js b/sidebars.js
index d1126022a3b..a0e4dcfcfcf 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -829,7 +829,7 @@ const sidebars = {
"reference-guides/best-practices/rancher-server/on-premises-rancher-in-vsphere",
"reference-guides/best-practices/rancher-server/rancher-deployment-strategy",
"reference-guides/best-practices/rancher-server/tips-for-running-rancher",
- "reference-guides/best-practices/rancher-server/tips-for-scaling-rancher"
+ "reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale"
]
},
{