> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/feature-guides/deployment-and-management/fleets.md).

# Fleets

Fleets let you manage collector operations and configurations at scale.

Collectors **inherit the configuration assigned to their Fleet** and can **join or leave Fleets without changing the Fleet’s configuration**.

Fleets were built to address common scaling and management needs:

* **Grouped config management** for sets of collectors
* **Label-based organization** by environment, geography, workload type, etc.
* **Install-time assignment** for container platforms using a Fleet label

### What are Fleets?

Fleet configurations take priority over any individual collector configuration. This makes it easy to manage settings for many collectors at once without having to update them individually.

If the fleet configuration is later removed or a collector leaves the fleet, the collector simply reverts to its fallback configuration. If no fallback configuration exists, it receives an empty configuration that does nothing. This means collectors will continue running with a known configuration rather than being left in an undefined state.

### Creating a Fleet

To create a fleet, go to the Fleets page and click `Create Fleet`.

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/Ce0MFRLWiJEO6Lg8x2pQ/NoFleet.png" alt=""><figcaption></figcaption></figure>

Select the collector type and platform and set a fleet name. (Optionally, you may specify a different resource name. This cannot be changed later.)

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/RDDelC3T9BG18sO41TNK/NewFleet02.png" alt=""><figcaption></figcaption></figure>

This creates an empty fleet to which you can assign a config or add collectors.

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/0gDgMc0JzmxQUOV9iTLF/NewFleet03.png" alt=""><figcaption></figcaption></figure>

#### CLI

Optionally, you can use the CLI to create a fleet. Define your fleet in a YAML file. Below is an explanation of the parameters.

| Parameter              | Description                                                                                                                                                                        |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `apiVersion`           | The API version of the resource being used. All Fleet resources currently use `bindplane.observiq.com/v1`.                                                                         |
| `kind`                 | Tells Bindplane what kind of resource it is dealing with. In this case, `Fleet`.                                                                                                   |
| `metadata.name`        | This is a unique identifier for your Fleet within Bindplane.                                                                                                                       |
| `metadata.displayName` | A friendly, readable name for your Fleet.                                                                                                                                          |
| `metadata.description` | An optional description of your Fleet to provide additional information.                                                                                                           |
| `metadata.labels`      | Labels attached to the Fleet resource that define which collectors can join the fleet. `platform` must match the operating system. `agent-type` must be `observiq-otel-collector`. |
| `spec.configuration`   | The resource name of the configuration assigned to the Fleet. This may be empty and assigned later.                                                                                |
| `selector.matchLabels` | Defines the matching rule for collectors. In this example, collectors with the label `fleet=lauras-test-fleet` will automatically be associated with this Fleet.                   |

```yaml
apiVersion: bindplane.observiq.com/v1
kind: Fleet
metadata:
    name: lauras-test-fleet
    displayName: Laura's Test Fleet
    description: This is just a test Fleet
    labels:
        platform: macos
        agent-type: observiq-otel-collector
spec:
    configuration: ""
    selector:
        matchLabels:
            fleet: lauras-test-fleet
```

Apply the fleet. For example:

```sh
bindplane apply lauras-test-fleet.yaml
```

Make sure the API key used to make this request has permission to create a fleet (requires project admin or project user permission).

### Adding Collectors to a Fleet

From the Fleet page, select `Add Collectors` and choose eligible collectors from the list.

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/UmnfmyqrNXTbWBtOBhl7/AddAgent.png" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
If a collector belongs to another fleet, it must be removed from the original fleet before adding it to a new one. A collector cannot belong to more than one fleet at a time.
{% endhint %}

Fleets may also be assigned when installing a new collector.

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/ulW72Icfbfb73VORYeSh/Agent02.png" alt=""><figcaption></figcaption></figure>

#### CLI

Optionally, you can add a collector to a fleet through the CLI by assigning the fleet label to the collector.

```sh
bindplane label collector <collector-id> fleet=<fleet-name>
```

### Assigning a Config to a Fleet

On the fleet page, choose `Assign Configuration`, and select your configuration. All collectors in the fleet will inherit the fleet configuration and use it immediately, if the configuration has been rolled out.

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/QnOfLhwGNw7rDlXPx1zQ/AddConfig.png" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Ensure your fleet’s configuration has been rolled out. Until then, collectors will continue to run on their individual configurations, if they exist.
{% endhint %}

To change the Fleet's configuration, choose `Change Configuration` and select the new config.

#### CLI

Optionally, you can assign a config to a fleet through the CLI by updating the YAML file with the new configuration name.

```yaml
apiVersion: bindplane.observiq.com/v1
kind: Fleet
metadata:
    name: lauras-test-fleet
    displayName: Laura's Test Fleet
    description: This is just a test Fleet
    labels:
        platform: macos
        agent-type: observiq-otel-collector
spec:
    configuration: Config-for-fleet
    selector:
        matchLabels:
            fleet: lauras-test-fleet
```

```sh
bindplane apply lauras-test-fleet.yaml
```

### Fleet Health & Metrics

The Fleet page includes collector health and telemetry insights to help you understand the overall state of your fleet.

The Telemetry Overview section displays hourly throughput for logs, metrics, and traces. Below this, you’ll find Collector Status and Collector Version tables, which show a breakdown of collectors by status and version. Clicking any status or version count will filter the collector table, allowing you to quickly focus on collectors with that specific status or version. To clear the filter and view all collectors assigned to the fleet, remove the text in the Collectors search bar.

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/czaOTdrlh3v2AaCxYbjx/Xnapper-2025-10-22-15.35.48.png" alt=""><figcaption></figcaption></figure>

### Removing Collectors from a Fleet

From the Fleet page, select the collectors you'd like to remove, choose `Remove Collectors` , and confirm.

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/ptTg7S3bV7jhLCiVFirW/RemoveAgent.png" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
When a collector is removed from a fleet, it will revert to the configuration it was previously assigned (its individual configuration label, if one exists).

If no previous configuration is available, the collector will receive an empty configuration that does nothing.

You can change a collector’s individual configuration label at any time using the Change Configuration button on the Collector page. If you update this label while the collector is assigned to a fleet, that new configuration becomes its fallback once the collector is removed from the fleet.
{% endhint %}

#### CLI

Optionally, you can remove a collector from a fleet through the CLI by removing the fleet label from the collector.

```sh
bindplane label collector <collector-id> fleet- --overwrite
```

### Deleting a Fleet

On the fleet page, choose `Delete` and confirm.

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/cJxs3BOOXFHuLsziCTrT/DeleteConfig02.png" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
All collectors must be removed from the fleet before the fleet can be deleted.
{% endhint %}

#### CLI

Optionally, you can delete the fleet through the CLI.

```sh
bindplane delete fleet lauras-test-fleet
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bindplane.com/feature-guides/deployment-and-management/fleets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.