Installer-Managed Control-Plane Updates
Understand how control-plane update detection, download, prepared state, apply, and rollback work in installer-managed deployments.
Installer-Managed Control-Plane Updates
Installer-managed control-plane updates are separate from agent updates.
Current model
- latest-only
- two-step
- installer-managed deployments only
The flow is:
The API compares the current installed releaseId to the latest published
releaseId.
A platform admin requests Download latest update.
The host-side supervisor fetches, verifies, extracts, and prepares the new
bundle under /opt/noderax-platform/releases/<releaseId>.
The prepared state becomes visible in the Control plane tab of the Updates
Center.
A platform admin explicitly confirms Apply prepared update.
The host-side supervisor recreates runtime services in a controlled order and verifies the new runtime before declaring success.
Apply-time UI behavior
While the control plane is actively applying:
- the authenticated web UI shows a full-screen freeze modal
- user interaction is intentionally blocked
- the modal shows live stage text, an approximate countdown, and refresh actions
This is not decorative. It exists because the web and API services may restart in place during the apply window.
Failure handling
If an apply fails, the host-side update flow attempts to:
- restore the previous bundle symlink
- reload the previous tagged images
- recreate the prior runtime
- surface the failure state back to the dashboard
Host state involved
TLS And Domain Setup
Use a public origin correctly, understand the ACME flow, and know how bundled nginx and certbot behave in installer-managed deployments.
Troubleshooting Install And Runtime Failures
Use the shipped status helper and the most common failure patterns to diagnose installer-managed control-plane issues.