deploy: ed074fe196

2026-09-27 13:38:07 +00:00 · 2024-05-23 14:53:36 +00:00
parent e5352ade2a
commit 9eb1c27bdf
5143 changed files with 15451 additions and 15423 deletions
@@ -324,8 +324,8 @@ const metadata = {
    "editUrl": "https://github.com/rancher/rancher-docs/edit/main/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md",
    "tags": [],
    "version": "2.7",
-    "lastUpdatedAt": 1716303542,
-    "formattedLastUpdatedAt": "May 21, 2024",
+    "lastUpdatedAt": 1716474317,
+    "formattedLastUpdatedAt": "May 23, 2024",
    "frontMatter": {
        "title": "Tuning and Best Practices for Rancher at Scale"
    },
@@ -391,6 +391,11 @@ const toc = [
        id: 'manage-upstream-cluster-nodes-directly-with-rke2',
        level: 3
    },
+    {
+        value: 'Keep all Upstream Cluster Nodes co-located',
+        id: 'keep-all-upstream-cluster-nodes-co-located',
+        level: 3
+    },
    {
        value: 'Keeping Kubernetes Versions Up to Date',
        id: 'keeping-kubernetes-versions-up-to-date',
@@ -605,6 +610,8 @@ function MDXContent(_param) {
    }, `Optimizations Outside of Rancher`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Important influencing factors are the underlying cluster's own performance and configuration. The upstream cluster, if misconfigured, can introduce a bottleneck Rancher software has no chance to resolve.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "manage-upstream-cluster-nodes-directly-with-rke2"
    }, `Manage Upstream Cluster Nodes Directly with RKE2`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `As Rancher can be very demanding on the upstream cluster, especially at scale, you should have full administrative control of the cluster's configuration and nodes. To identify the root cause of excess resource consumption, use standard Linux troubleshooting techniques and tools. This can aid in distinguishing between whether Rancher, Kubernetes, or operating system components are causing issues. `), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Although managed Kubernetes services make it easier to deploy and run Kubernetes clusters, they are discouraged for the upstream cluster in high scale scenarios. Managed Kubernetes services typically limit access to configuration and insights on individual nodes and services.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Use RKE2 for large scale use cases.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
+        "id": "keep-all-upstream-cluster-nodes-co-located"
+    }, `Keep all Upstream Cluster Nodes co-located`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `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.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Traffic between Rancher components and the Kubernetes API is especially sensitive to network latency, as is etcd traffic between nodes.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `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.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "keeping-kubernetes-versions-up-to-date"
    }, `Keeping Kubernetes Versions Up to Date`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `You should keep the local Kubernetes cluster up to date. This will ensure that your cluster has all available performance enhancements and bug fixes.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "optimizing-etcd"
@@ -324,8 +324,8 @@ const metadata = {
    "editUrl": "https://github.com/rancher/rancher-docs/edit/main/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md",
    "tags": [],
    "version": "current",
-    "lastUpdatedAt": 1716303542,
-    "formattedLastUpdatedAt": "May 21, 2024",
+    "lastUpdatedAt": 1716474317,
+    "formattedLastUpdatedAt": "May 23, 2024",
    "frontMatter": {
        "title": "Tuning and Best Practices for Rancher at Scale"
    },
@@ -391,6 +391,11 @@ const toc = [
        id: 'manage-upstream-cluster-nodes-directly-with-rke2',
        level: 3
    },
+    {
+        value: 'Keep all Upstream Cluster Nodes co-located',
+        id: 'keep-all-upstream-cluster-nodes-co-located',
+        level: 3
+    },
    {
        value: 'Keeping Kubernetes Versions Up to Date',
        id: 'keeping-kubernetes-versions-up-to-date',
@@ -605,6 +610,8 @@ function MDXContent(_param) {
    }, `Optimizations Outside of Rancher`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Important influencing factors are the underlying cluster's own performance and configuration. The upstream cluster, if misconfigured, can introduce a bottleneck Rancher software has no chance to resolve.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "manage-upstream-cluster-nodes-directly-with-rke2"
    }, `Manage Upstream Cluster Nodes Directly with RKE2`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `As Rancher can be very demanding on the upstream cluster, especially at scale, you should have full administrative control of the cluster's configuration and nodes. To identify the root cause of excess resource consumption, use standard Linux troubleshooting techniques and tools. This can aid in distinguishing between whether Rancher, Kubernetes, or operating system components are causing issues. `), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Although managed Kubernetes services make it easier to deploy and run Kubernetes clusters, they are discouraged for the upstream cluster in high scale scenarios. Managed Kubernetes services typically limit access to configuration and insights on individual nodes and services.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Use RKE2 for large scale use cases.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
+        "id": "keep-all-upstream-cluster-nodes-co-located"
+    }, `Keep all Upstream Cluster Nodes co-located`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `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.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Traffic between Rancher components and the Kubernetes API is especially sensitive to network latency, as is etcd traffic between nodes.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `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.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "keeping-kubernetes-versions-up-to-date"
    }, `Keeping Kubernetes Versions Up to Date`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `You should keep the local Kubernetes cluster up to date. This will ensure that your cluster has all available performance enhancements and bug fixes.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "optimizing-etcd"
@@ -324,8 +324,8 @@ const metadata = {
    "editUrl": "https://github.com/rancher/rancher-docs/edit/main/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md",
    "tags": [],
    "version": "2.8",
-    "lastUpdatedAt": 1716303542,
-    "formattedLastUpdatedAt": "May 21, 2024",
+    "lastUpdatedAt": 1716474317,
+    "formattedLastUpdatedAt": "May 23, 2024",
    "frontMatter": {
        "title": "Tuning and Best Practices for Rancher at Scale"
    },
@@ -391,6 +391,11 @@ const toc = [
        id: 'manage-upstream-cluster-nodes-directly-with-rke2',
        level: 3
    },
+    {
+        value: 'Keep all Upstream Cluster Nodes co-located',
+        id: 'keep-all-upstream-cluster-nodes-co-located',
+        level: 3
+    },
    {
        value: 'Keeping Kubernetes Versions Up to Date',
        id: 'keeping-kubernetes-versions-up-to-date',
@@ -605,6 +610,8 @@ function MDXContent(_param) {
    }, `Optimizations Outside of Rancher`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Important influencing factors are the underlying cluster's own performance and configuration. The upstream cluster, if misconfigured, can introduce a bottleneck Rancher software has no chance to resolve.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "manage-upstream-cluster-nodes-directly-with-rke2"
    }, `Manage Upstream Cluster Nodes Directly with RKE2`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `As Rancher can be very demanding on the upstream cluster, especially at scale, you should have full administrative control of the cluster's configuration and nodes. To identify the root cause of excess resource consumption, use standard Linux troubleshooting techniques and tools. This can aid in distinguishing between whether Rancher, Kubernetes, or operating system components are causing issues. `), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Although managed Kubernetes services make it easier to deploy and run Kubernetes clusters, they are discouraged for the upstream cluster in high scale scenarios. Managed Kubernetes services typically limit access to configuration and insights on individual nodes and services.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Use RKE2 for large scale use cases.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
+        "id": "keep-all-upstream-cluster-nodes-co-located"
+    }, `Keep all Upstream Cluster Nodes co-located`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `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.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Traffic between Rancher components and the Kubernetes API is especially sensitive to network latency, as is etcd traffic between nodes.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `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.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "keeping-kubernetes-versions-up-to-date"
    }, `Keeping Kubernetes Versions Up to Date`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `You should keep the local Kubernetes cluster up to date. This will ensure that your cluster has all available performance enhancements and bug fixes.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "optimizing-etcd"
@@ -324,8 +324,8 @@ const metadata = {
    "editUrl": "https://github.com/rancher/rancher-docs/edit/main/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md",
    "tags": [],
    "version": "2.6",
-    "lastUpdatedAt": 1716303542,
-    "formattedLastUpdatedAt": "May 21, 2024",
+    "lastUpdatedAt": 1716474317,
+    "formattedLastUpdatedAt": "May 23, 2024",
    "frontMatter": {
        "title": "Tuning and Best Practices for Rancher at Scale"
    },
@@ -391,6 +391,11 @@ const toc = [
        id: 'manage-upstream-cluster-nodes-directly-with-rke2',
        level: 3
    },
+    {
+        value: 'Keep all Upstream Cluster Nodes co-located',
+        id: 'keep-all-upstream-cluster-nodes-co-located',
+        level: 3
+    },
    {
        value: 'Keeping Kubernetes Versions Up to Date',
        id: 'keeping-kubernetes-versions-up-to-date',
@@ -605,6 +610,8 @@ function MDXContent(_param) {
    }, `Optimizations Outside of Rancher`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Important influencing factors are the underlying cluster's own performance and configuration. The upstream cluster, if misconfigured, can introduce a bottleneck Rancher software has no chance to resolve.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "manage-upstream-cluster-nodes-directly-with-rke2"
    }, `Manage Upstream Cluster Nodes Directly with RKE2`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `As Rancher can be very demanding on the upstream cluster, especially at scale, you should have full administrative control of the cluster's configuration and nodes. To identify the root cause of excess resource consumption, use standard Linux troubleshooting techniques and tools. This can aid in distinguishing between whether Rancher, Kubernetes, or operating system components are causing issues. `), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Although managed Kubernetes services make it easier to deploy and run Kubernetes clusters, they are discouraged for the upstream cluster in high scale scenarios. Managed Kubernetes services typically limit access to configuration and insights on individual nodes and services.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Use RKE2 for large scale use cases.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
+        "id": "keep-all-upstream-cluster-nodes-co-located"
+    }, `Keep all Upstream Cluster Nodes co-located`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `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.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `Traffic between Rancher components and the Kubernetes API is especially sensitive to network latency, as is etcd traffic between nodes.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `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.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "keeping-kubernetes-versions-up-to-date"
    }, `Keeping Kubernetes Versions Up to Date`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("p", null, `You should keep the local Kubernetes cluster up to date. This will ensure that your cluster has all available performance enhancements and bug fixes.`), /*#__PURE__*/ (0,_mdx_js_react__WEBPACK_IMPORTED_MODULE_1__/* .mdx */ .kt)("h3", {
        "id": "optimizing-etcd"
--- a/Show More
+++ b/Show More