Agent And Control-Plane Update Flows
Distinguish the rollout-based agent update APIs from installer-managed control-plane update APIs.
Agent And Control-Plane Update Flows
Noderax has two update domains.
Agent updates
Agent updates are rollout-driven. They target enrolled nodes and report rollout progress back into the control plane.
Control-plane updates
Control-plane updates are installer-managed and host-executed. The API only:
- summarizes update availability
- queues download/apply requests
- exposes state back to the web UI
The actual deployment mutation happens on the host-side supervisor.
Agent updates are fleet operations. They target many nodes, move progressively, and remain scoped to enrolled agent runtimes.
Control-plane updates are host-local bundle operations. They prepare and apply a new installer-managed platform bundle for the control plane itself.
Decision boundary
API design consequences
Agent update APIs
Expose release discovery, rollout creation, rollout monitoring, and rollback-oriented fleet operations.
Control-plane update APIs
Expose summary/download/apply only. The API is intentionally not the component that mutates the Docker runtime.