From 56ca46001c876e1aa945557f4a27e2b51869576b Mon Sep 17 00:00:00 2001 From: hridyesh bisht Date: Fri, 20 Mar 2026 16:37:01 +0530 Subject: [PATCH 1/5] Adding information about Fleet resource limits --- .../integrations-in-rancher/fleet/overview.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md b/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md index efe2f2fd2f4..4881872fefc 100644 --- a/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md +++ b/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md @@ -58,7 +58,13 @@ For details on using Fleet behind a proxy, see the [Using Fleet Behind a Proxy]( In order for Helm charts with dependencies to deploy successfully, you must run a manual command (as listed below), as it is up to the user to fulfill the dependency list. If you do not do this and proceed to clone your repository and run `helm install`, your installation will fail because the dependencies will be missing. -The Helm chart in the git repository must include its dependencies in the charts subdirectory. You must either manually run `helm dependencies update $chart` or run `helm dependencies build $chart` locally, then commit the complete charts directory to your git repository. Note that you will update your commands with the applicable parameters +The Helm chart in the git repository must include its dependencies in the charts subdirectory. You must either manually run `helm dependencies update $chart` or run `helm dependencies build $chart` locally, then commit the complete charts directory to your git repository. Note that you will update your commands with the applicable parameters. + +## Fleet resource configuration + +Fleet supports configuring CPU and memory resource requests and limits for both management cluster controllers and downstream cluster agents. When running Fleet through Rancher, pass configuration using the rancher-config ConfigMap instead of Helm directly. + +For detailed configuration options, refer to [Resource Limits in Fleet](https://fleet.rancher.io/how-tos-for-operators/resource-limits) ## Troubleshooting From cdd40292a4cce31dbb8d99425591d567c64851d3 Mon Sep 17 00:00:00 2001 From: hridyesh bisht <41201308+kakabisht@users.noreply.github.com> Date: Mon, 23 Mar 2026 14:06:56 +0530 Subject: [PATCH 2/5] Update versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md Co-authored-by: Lucas Saintarbor --- .../version-2.14/integrations-in-rancher/fleet/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md b/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md index 4881872fefc..bbb24013e62 100644 --- a/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md +++ b/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md @@ -58,7 +58,7 @@ For details on using Fleet behind a proxy, see the [Using Fleet Behind a Proxy]( In order for Helm charts with dependencies to deploy successfully, you must run a manual command (as listed below), as it is up to the user to fulfill the dependency list. If you do not do this and proceed to clone your repository and run `helm install`, your installation will fail because the dependencies will be missing. -The Helm chart in the git repository must include its dependencies in the charts subdirectory. You must either manually run `helm dependencies update $chart` or run `helm dependencies build $chart` locally, then commit the complete charts directory to your git repository. Note that you will update your commands with the applicable parameters. +The Helm chart in the git repository must include its dependencies in the `charts/` subdirectory. To do this, manually run `helm dependencies update $chart` or run `helm dependencies build $chart` locally, then commit the complete `charts/` directory to your git repository. Ensure you update your commands with the applicable parameters to your environment. ## Fleet resource configuration From 5be76d49c9b5eedb5b1a873a948a46ac758fa2e5 Mon Sep 17 00:00:00 2001 From: hridyesh bisht <41201308+kakabisht@users.noreply.github.com> Date: Mon, 23 Mar 2026 14:07:03 +0530 Subject: [PATCH 3/5] Update versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md Co-authored-by: Lucas Saintarbor --- .../version-2.14/integrations-in-rancher/fleet/overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md b/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md index bbb24013e62..03351299ac2 100644 --- a/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md +++ b/versioned_docs/version-2.14/integrations-in-rancher/fleet/overview.md @@ -62,9 +62,9 @@ The Helm chart in the git repository must include its dependencies in the `chart ## Fleet resource configuration -Fleet supports configuring CPU and memory resource requests and limits for both management cluster controllers and downstream cluster agents. When running Fleet through Rancher, pass configuration using the rancher-config ConfigMap instead of Helm directly. +Fleet allows you to configuring CPU and memory resource requests and limits for both management cluster controllers and downstream cluster agents. When running Fleet through Rancher, apply these changes using the `rancher-config` ConfigMap rather than via Helm directly. -For detailed configuration options, refer to [Resource Limits in Fleet](https://fleet.rancher.io/how-tos-for-operators/resource-limits) +For detailed configuration options, refer to [Resource Limits in Fleet](https://fleet.rancher.io/how-tos-for-operators/resource-limits). ## Troubleshooting From 333dcfe06cac507fd1e306e1de63dd19065a6642 Mon Sep 17 00:00:00 2001 From: hridyesh bisht Date: Mon, 23 Mar 2026 14:24:18 +0530 Subject: [PATCH 4/5] Adding information in docs --- docs/integrations-in-rancher/fleet/overview.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/integrations-in-rancher/fleet/overview.md b/docs/integrations-in-rancher/fleet/overview.md index efe2f2fd2f4..5da64f96a1d 100644 --- a/docs/integrations-in-rancher/fleet/overview.md +++ b/docs/integrations-in-rancher/fleet/overview.md @@ -60,6 +60,12 @@ In order for Helm charts with dependencies to deploy successfully, you must run The Helm chart in the git repository must include its dependencies in the charts subdirectory. You must either manually run `helm dependencies update $chart` or run `helm dependencies build $chart` locally, then commit the complete charts directory to your git repository. Note that you will update your commands with the applicable parameters +## Fleet resource configuration + +Fleet allows you to configuring CPU and memory resource requests and limits for both management cluster controllers and downstream cluster agents. When running Fleet through Rancher, apply these changes using the `rancher-config` ConfigMap rather than via Helm directly. + +For detailed configuration options, refer to [Resource Limits in Fleet](https://fleet.rancher.io/how-tos-for-operators/resource-limits). + ## Troubleshooting - **Known Issue**: clientSecretName and helmSecretName secrets for Fleet gitrepos are not included in the backup nor restore created by the [backup-restore-operator](../../how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/back-up-rancher.md#1-install-the-rancher-backup-operator). We will update the community once a permanent solution is in place. From 1ea36823423e57c7c9ffe0f385806b3f6c0450e2 Mon Sep 17 00:00:00 2001 From: hridyesh bisht <41201308+kakabisht@users.noreply.github.com> Date: Mon, 23 Mar 2026 22:43:55 +0530 Subject: [PATCH 5/5] Update docs/integrations-in-rancher/fleet/overview.md Co-authored-by: Lucas Saintarbor --- docs/integrations-in-rancher/fleet/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations-in-rancher/fleet/overview.md b/docs/integrations-in-rancher/fleet/overview.md index 5da64f96a1d..03351299ac2 100644 --- a/docs/integrations-in-rancher/fleet/overview.md +++ b/docs/integrations-in-rancher/fleet/overview.md @@ -58,7 +58,7 @@ For details on using Fleet behind a proxy, see the [Using Fleet Behind a Proxy]( In order for Helm charts with dependencies to deploy successfully, you must run a manual command (as listed below), as it is up to the user to fulfill the dependency list. If you do not do this and proceed to clone your repository and run `helm install`, your installation will fail because the dependencies will be missing. -The Helm chart in the git repository must include its dependencies in the charts subdirectory. You must either manually run `helm dependencies update $chart` or run `helm dependencies build $chart` locally, then commit the complete charts directory to your git repository. Note that you will update your commands with the applicable parameters +The Helm chart in the git repository must include its dependencies in the `charts/` subdirectory. To do this, manually run `helm dependencies update $chart` or run `helm dependencies build $chart` locally, then commit the complete `charts/` directory to your git repository. Ensure you update your commands with the applicable parameters to your environment. ## Fleet resource configuration