> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/operate/fleet-manager.md).

# Fleet Manager

The fleet manager service is a backend component that is in charge of managing groundcover's entities throughout the different clusters managed by the backend.

## Enabling the Fleet Manager

To enable the fleet manager, your `values.yaml` file should contain:

```
global:
  fleetmanager:
    enabled: true
```

If you use our [BYOC](/collect-data/byoc.md) service, we will enable the fleet manager for you. However, the above is still needed for groundcover's sensors in your environments to connect to the fleet manager.

If you manage your own backend, for example in [on-premise](/collect-data/customize-deployment/on-premise-deployment.md) and in [air-gapped](/architecture/overview.md#airgapped) deployments, the above configuration will enable the fleet manager deployment as well as configure the sensors to connect to it.

## Remote Configuration

Remote configuration is a mechanism that allows groundcover's services, including sensors, to be configured dynamically and remotely. The configurations are stored alongside the fleet manager and are passed from the fleet manager to the services.

{% hint style="info" %}
For remote configuration to work, services need to be able to communicate with the fleet manager. For this, they need to be configured with a suitable [ingestion key](/collect-data/ingestion-keys.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/operate/fleet-manager.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.