Skip to main content
Use node lifecycle actions when you need to change whether a node is active, restart it, prepare it for shutdown, move it out of an enterprise, delete it, or export Edge Sync configuration.

​
Where Lifecycle Actions Appear

You can run node actions from:
  • The row action menu in Infrastructure > Fleet > Nodes.
  • The More actions menu on a node detail page.
  • The bulk action menu on the Nodes list for supported multi-node actions.
Bulk actions support several lifecycle operations, but Update EVE-OS is disabled for bulk selection. Update EVE-OS one node at a time. Download Edge Sync Config is the exception: this action appears only in the More actions menu on a node detail page. It is not in the row action menu on the Nodes list, and it is not a bulk action. See Download Edge Sync Config for the steps.

​
Action Reference

​
Activate a Node

  1. Open Infrastructure > Fleet > Nodes.
  2. Select the node row action menu, or open the node and select More actions.
  3. Select Activate.
  4. Confirm the action if prompted.
Use activation when the node was created inactive, manually deactivated, or needs to return to operation.

​
Deactivate a Node

  1. Open the node row action menu or the detail More actions menu.
  2. Select Deactivate.
  3. Review the confirmation dialog.
  4. Confirm the action.
Deactivation can make Applications unavailable. Check Workloads before deactivating a production node. You cannot deactivate a node that belongs to an Edge Node Cluster. Edge Infrastructure Services refuses the request, and the node event log records failed to deactivate a device as the device is part of a cluster. The console does not remove a node from a cluster. If you need to deactivate a cluster member, replace it in the cluster first, or delete the cluster. See Replace a Node.

​
Reboot a Node

  1. Open the node row action menu or the detail More actions menu.
  2. Select Reboot.
  3. Review the confirmation dialog.
  4. Confirm the action.
During reboot, the node and Applications running on it might be unavailable for a short time. For a node that belongs to an Edge Node Cluster, Edge Infrastructure Services refuses the reboot while any other member of the cluster is not online, so that no more than one cluster node is offline at a time. The error names the member that is offline, for example device node-2 is not online. No more than one device in cluster can be offline. Wait for the other member to come back online, then retry the reboot. To update EVE-OS on cluster members, use the cluster upgrade instead of rebooting nodes individually. See Manage Node Clusters.

​
Prepare Power Off

  1. Open the node row action menu or the detail More actions menu.
  2. Select Prepare Power Off.
  3. Review the confirmation dialog.
  4. Confirm the action.
Use this before a planned physical shutdown. Applications halted by this action should resume their previous state after the node is powered back on.

​
Off-board a Node

  1. Before off-boarding, open the node detail page.
  2. Review Workloads and remove resources that should not remain attached.
  3. Open the row action menu or detail More actions menu.
  4. Select Off-board.
  5. Review the confirmation dialog.
  6. Confirm the action.
Off-boarding is different from deleting. Off-boarding is used when the device identity should be retained for re-onboarding, such as moving a node between enterprises or deployment sites. For EVE-k deployments, keep the same node name during off-board and re-onboard workflows. Kubernetes storage and workload components can depend on stable node naming.

​
Delete a Node

Before you delete a node, check the following prerequisites:
  • Remove the node from its cluster. You can’t delete a node that belongs to an Edge Node Cluster. The delete dialog blocks the action and names the cluster. The console does not remove a node from a cluster, so replace the node in the cluster or delete the cluster first, then delete the node. See Replace a Node.
  • Get permission to delete the node’s dependents. If the node has app instances, virtual networks, or volumes, the delete also removes them. You need delete permission for application instances in the node’s project. Without it, the dialog blocks the delete. Remove those resources first, or ask a user with that permission to delete the node.
  • Reduce the dependents to 50 or fewer per type. The delete dialog can review at most 50 dependents in each category (application instances, virtual networks, and volumes). If any category has more than 50, the dialog blocks the delete and reports the counts, for example This node has more dependents than can be reviewed here (72 applications). Delete some of those resources manually, then try deleting the node again.
  1. Open the row action menu or detail More actions menu.
  2. Select Delete.
  3. Review the cascade impact and confirmation dialog.
  4. Confirm the action only when you are sure the node identity should be removed.
The console attempts to delete every dependent, then attempts to delete the node even if some dependents couldn’t be deleted. Some dependents can’t be deleted manually. For example, a base-image volume rejects manual deletion, but Edge Infrastructure Services removes it along with the node. The delete ends in one of three outcomes: The Deleted N of M count includes the node only when the node itself was deleted. Deleting removes the node identity from Edge Infrastructure Services. Re-onboarding the same physical device might require resetting device identity on the device.

​
Download Edge Sync Config

Download Edge Sync Config is available only from the More actions menu on a node detail page. It is not in the row action menu on the Nodes list, and it is not a bulk action, so download the configuration one node at a time. This is a read action. You can run it with read permission on the node, and it does not require update permission.
  1. Confirm Edge Sync is configured for the node.
  2. Open Infrastructure > Fleet > Nodes and click the node name to open the detail page.
  3. In the node detail page header, select More actions (the ... button).
  4. Select Download Edge Sync Config.
  5. Save the downloaded file for the Edge Sync workflow.
The menu item shows a spinner while the download is in progress. If the download fails, verify that you have read permission for the node and that Edge Sync is configured for it. For the full download and import workflow, see Configure Edge Synchronization.

​
Verify the Result

After any lifecycle action:
  • Return to Infrastructure > Fleet > Nodes.
  • Refresh or wait for the table to update.
  • Confirm the node status and admin state match the requested action.
  • Open the node detail page if the status does not change as expected.
  • Check View Events and Configuration Status for errors or delayed changes.

​
Next Steps