Add Node And Bootstrap Flow
Add a node from the dashboard, run the generated install command, and understand how install progress and final enrollment are reported.
Add Node And Bootstrap Flow
Node enrollment is a two-sided workflow between the control plane and the agent install command.
Control-plane side
When you add a node in the dashboard, the control plane creates:
- an enrollment context
- a node install record
- an install command tailored to the current public API URL
The install command must use an externally reachable API URL, not an internal container hostname.
If the generated install command contains an internal hostname such as
http://nginx, the node cannot enroll from outside the control-plane host.
Current builds prefer the public API URL derived from the active public origin.
Node-side execution
Running the generated install command on the target machine installs the agent, registers it, and reports progress back to the control plane.
Progress model
Recent fixes hardened the realtime path for node-install progress:
- workspace room fanout exists in HA mode
- cross-instance Redis bridge forwards events
- node install progress is emitted immediately instead of waiting behind a slow outbox path
Enrollment flow
A platform user creates the node enrollment in the dashboard.
The API generates a node install command scoped to the active workspace and public API URL.
The operator runs the command on the target machine.
The agent installs, authenticates, emits bootstrap progress, and completes final registration.
What the operator should expect to see
Related pages
Users, Memberships, Teams, And Roles
Understand how the control plane scopes operational access and why workspace-aware behavior matters throughout the product.
Metrics, Events, Diagnostics, And Notifications
Use the operational observability surfaces and understand how live metric updates and workspace-scoped events move through the system.