Connect and Manage Your Fleet
Expanso Cloud connects pipeline management to the hosts where your data lives. Register an Expanso Edge node with a workspace, confirm that it is connected, and select which pipelines it should run.
Add a node
Open Nodes → Add Node in the intended workspace. Cloud offers instructions to:
- Install and bootstrap Expanso Edge.
- Bootstrap an existing installation.
- Run Expanso Edge in Docker.
Choose a token validity period and copy the instructions appropriate to your host. For a non-Docker installation, follow the provided instructions to start Expanso Edge after bootstrap. A successful installation alone does not prove that the node has connected to Cloud.
Return to the node list and verify the connection state. The node quickstart provides the full onboarding walkthrough.
Manage bootstrap tokens
Bootstrap tokens enroll nodes into a particular workspace. Under Keys, you can create tokens with a description and expiry, inspect their creation and last-use information, and revoke them. Non-expiring tokens are available when that fits your enrollment process; time-limited tokens are useful for bounded installation work.
Store tokens securely. An API key and a bootstrap token have different purposes: use an API key for CLI or API operations.
Inspect fleet health
The fleet view summarizes connected, disconnected, and lost nodes and the connected share of the fleet. Filter the node table by connection state or operating system, refresh it, and choose the columns useful to your team.
Open a node to inspect its hostname, operating system, architecture, agent version, last heartbeat, connection timestamps, status message, labels, and executions. These details help distinguish an unavailable host from a pipeline problem on an otherwise connected node.
The node Monitoring view provides CPU utilization and memory usage over a selected time range. For connection timing, see workspace settings.
Select deployment targets
The pipeline deployment form supports:
| Selector | Use |
|---|---|
| Matching labels | Select nodes with the required key/value properties; all label constraints must match. |
| Expressions | Select by conditions such as membership, absence, or inequality. |
| Explicit node IDs | Choose particular nodes for a deployment. |
With no selector constraints, the pipeline targets all eligible nodes in the workspace. Review this choice before deploying a job intended for a single site or test host.
Labels and selectors let the same pipeline logic serve different host groups. They describe placement; they do not copy host files, provision external services, or change source permissions.
Remove a node record
The node table supports selected-node deletion with confirmation. Review which records are selected before confirming. Treat node-record removal separately from uninstalling software or shutting down a host; do not assume the console has performed those host operations.
