Agent Line And Rollouts
Track the separate operational model for agent releases and understand how it differs from control-plane self-update.
Agent Line And Rollouts
Agent releases remain a separate concern from control-plane releases.
Agent release behavior
- agents are updated through rollout APIs and UI surfaces
- rollouts target enrolled nodes
- progress is observable from the dashboard and API
- rollback behavior is independent from host-side control-plane rollback
A rollout changes the node-side runtime. That means telemetry shipping, task execution, package operations, terminal transport, and agent-side bug fixes all move with the rollout.
A rollout does not replace the control plane, the installer-managed bundle, nginx, PostgreSQL, Redis, or the host-side runtime supervisor.
Why the split matters
Treating agent updates and control-plane updates as one surface would hide real operational differences. Noderax keeps them separate because:
- agent updates change node runtimes
- control-plane updates change the platform itself
- each one has different safety constraints, scopes, and recovery paths
Recent Platform Changes
Summarize the major recent changes that affected installer-managed deployments, runtime promotion, updates, and realtime behavior.
Users, Memberships, Teams, And Roles
Understand how the control plane scopes operational access and why workspace-aware behavior matters throughout the product.