Skip to content
- Read the release notes. Note breaking changes, migration steps, and
minimum versions.
- Back up the database (admin backups). This is the
rollback for everything except node agents.
- Update the panel — pull the new images and recreate containers. Database
migrations run automatically at backend startup; watch the logs until they
complete.
- Verify the panel: log in, open a server console, check a backup listing.
- Update nodes one batch at a time (updating a node).
- Never update everything at once. Panel first, one canary node, then the fleet.
- Never skip the pre-update database backup, even for “tiny” releases.
- Pin production to release tags, not
main. Track main only in a lab.
- If the panel fails to start after an update, read the container logs before
doing anything — most failures are a migration waiting on a lock or an env
variable renamed in the release notes.
- Panel: restore the database backup, then restart the previous images.
- Nodes: reinstall the previous agent build on the affected node.
- After any rollback, verify the same four checks as an update before
declaring victory.
