Skip to main content
Use fleets when multiple provider nodes should be managed and admitted as a group. A fleet belongs to an account. Nodes in that fleet must also belong to the same account.

​
1. Create a fleet

Output includes the fleet ID. Use that ID for the remaining commands.

​
2. List fleets

​
3. Show one fleet

​
4. Join a node through the fleet

Run this command on the machine that will provide capacity:
When --fleet is present, provider admission is evaluated through the fleet. The command creates or loads the local node identity and proves ownership from the machine before adding it to the fleet. The optional display name is presentation metadata; fleet membership still uses the canonical node ID.

​
5. List fleet nodes

Output similar to:
The full node ID remains visible and is the value used by fleet, admission, and placement commands. Display names can be duplicated and cannot be used as node arguments.

​
6. Grant the fleet admission to a subnet

If you operate the subnet, grant provider admission to the fleet:
Subnet operators can also grant admission to one specific node:
Use direct node admission when one machine should be admitted without admitting the whole fleet.

​
7. Remove a node from the fleet

Removing a node from a fleet changes future fleet-based admission decisions. It does not delete the node identity from the machine.