Fleet Operations
Fleet Operations lets you issue commands to Cloud OS instances from the Control Panel. Commands are queued, tracked through their lifecycle, and can target individual servers or groups of instances in bulk.
Command System
The Control Panel uses a command queue model. When you issue a command, it is placed in a queue and delivered to the target instance via the mTLS agent connection. The instance executes the command and reports the result back.
Command Lifecycle
Every command moves through these statuses:
| Status | Description |
|---|---|
| Pending | Command created and waiting to be delivered to the instance |
| Running | Command has been delivered and is executing on the instance |
| Completed | Command finished successfully |
| Failed | Command execution failed (error details available) |
┌─────────┐ ┌─────────┐ ┌───────────┐ ┌──────────┐
│ Pending │───►│ Running │───►│ Completed │ │ Failed │
└─────────┘ └─────────┘ └───────────┘ └──────────┘
│ ▲
└───────────────────────────────┘Issuing a Command
- Navigate to Fleet Operations from the sidebar
- Click New Command
- Select the target — a single instance, a group, or a tag-based filter
- Choose the command type
- Configure command parameters
- Click Execute
The command appears in the operations queue with its status updating in real time.
Command Types
The Control Panel supports several categories of commands:
App Management
- Install App — install an application from the app template catalog on the target instance
- Uninstall App — remove an installed application
- Update App — update an application to a newer template version
- Start / Stop / Restart App — control the lifecycle of an installed application
System Operations
- Update Cloud OS — trigger a binary update on the target instance
- Restart Cloud OS — restart the Cloud OS service
- Run Health Check — request an immediate health report from the instance
Configuration
- Apply Config — push configuration changes to an instance
- Sync Settings — synchronize settings from a baseline configuration
Bulk Operations
You can target multiple instances with a single command by selecting:
- Group — all instances in a named group
- Tag filter — all instances matching a tag query (e.g.,
env=production) - All instances — every registered instance in the fleet
When a bulk command is issued, the Control Panel creates individual command entries for each target instance. You can track the overall progress and see per-instance results.
Bulk operations execute commands in parallel across all targeted instances. Use caution with destructive commands like uninstall or OS updates on production fleets. Consider using canary deployments via the Governance system for safer rollouts.
App Template Catalog Distribution
The Control Panel maintains a centralized catalog of app templates that can be distributed to Cloud OS instances. When you install an app via Fleet Operations, the template is delivered to the target instance along with the install command.
This allows you to maintain a curated set of approved applications and deploy them consistently across your fleet.
Command History
The Command History tab shows all previously issued commands with:
- Command type and parameters
- Target instance or group
- Status (pending, running, completed, failed)
- Timestamp of creation and completion
- Error details for failed commands
You can filter the history by status, command type, target, and date range.
Queue Management
Canceling Commands
Pending commands that have not yet been delivered can be canceled from the command queue. Once a command reaches “running” status, it cannot be canceled from the Control Panel.
Retry Failed Commands
Failed commands can be retried with a single click. The Control Panel creates a new command entry with the same parameters.
Offline Instance Handling
Commands targeted at offline instances remain in “pending” status. When the instance reconnects and sends a heartbeat, pending commands are delivered automatically.
The command queue is persistent. Pending commands survive Control Panel restarts and will be delivered when the target instance comes back online.
Next Steps
- Fleet Management — register and monitor your instances
- Governance — enforce policies and automate deployments