Adding information about Fleet resource limits

This commit is contained in:
hridyesh bisht
2026-03-20 16:37:01 +05:30
parent 2b7f6179cd
commit 56ca46001c
@@ -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