Fleet deployment
Upgrade or remove an agent
Change agent versions without losing host identity or SSH recovery access.
Upgrades should preserve the host's durable mTLS identity and managed state. Removing a host should revoke its Tenvyr identity before local files are discarded.
Upgrade
- Verify the new package and read its compatibility notes.
- Test upgrade and rollback in the lab.
- Confirm a recovery SSH path.
- Stop the agent service.
- Back up its root-owned state using your approved secure process.
- Upgrade the package without replacing
identity.json. - Start the service and confirm heartbeat and reconciliation.
- Validate
sshdand perform a canary SSH connection.
If the package changes the managed manifest key or root, qualify the migration as a configuration change rather than a routine binary upgrade.
Roll back
Roll back the executable and service definition while preserving the compatible host identity. Restore the last known-good managed SSH configuration, validate it, and reload OpenSSH. If identity compatibility is uncertain, contain the host in Tenvyr and use the independent recovery path.
Remove
- Remove the host from active access policies or contain it.
- Stop and disable the agent.
- Restore or remove Tenvyr-managed SSH configuration.
- Validate and reload OpenSSH.
- Revoke or remove the host identity in Tenvyr.
- Remove package, service, state, and empty enrollment placeholder according to your retention policy.
- Confirm the host no longer accepts Tenvyr-issued access.
Deleting only the local package is not a complete offboarding workflow.