> ## Documentation Index > Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL. > Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other. > Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking. > Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify. # Manage Node Lifecycle > Operate node lifecycle actions such as activate, deactivate, reboot, prepare power off, off-board, delete, and download Edge Sync config. 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](#download-edge-sync-config) for the steps. ## Action Reference | Action | Use it when | Verify | | - | - | - | | **Activate** | The node should be allowed to operate and connect. | Admin state moves toward active or registered and status reports normally. | | **Deactivate** | You need to stop the node from normal operation. | Admin state becomes inactive and Applications might stop. | | **Reboot** | You need to restart the node to recover or apply changes. | Status changes during reboot, then returns to online when healthy. | | **Prepare Power Off** | You need a graceful shutdown path before removing power. | Applications halt and should resume their prior state after power is restored. | | **Off-board** | You need to remove the node from the enterprise while preserving device identity for re-onboarding. | The node is archived or removed from active inventory according to the action result. | | **Delete** | You no longer need the node identity in Edge Infrastructure Services. | The node disappears from the list. Re-onboarding might require resetting device identity. | | **Download Edge Sync Config** | Edge Sync is configured and you need the node's sync configuration. | The config file downloads. | ## 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](https://zededa.mintlify.site/new-ui/infrastructure-services/node-clusters/manage-node-clusters.md#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](https://zededa.mintlify.site/new-ui/infrastructure-services/node-clusters/manage-node-clusters.md). ## 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](https://zededa.mintlify.site/new-ui/infrastructure-services/node-clusters/manage-node-clusters.md#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: | Outcome | What you see | What to do | | - | - | - | | **Node and all dependents deleted** | The dialog closes and a success notification appears. | Nothing. | | **Node deleted, some dependents remain** | The dialog closes and a success notification appears. A second, persistent notification lists the leftover resources: `Deleted, but these need to be cleaned up manually: …` | Review each listed resource and delete it manually if it still exists. Dismiss the notification when you're done. | | **Node not deleted** | The dialog stays open and lists each error. Errors for dependents (for example, `App instance : `) appear first, followed by the node error (`Node: `). A persistent notification summarizes how many resources were deleted (for example, **Deleted 2 of 5**) and the reason. | Fix the listed errors, then try deleting the node again. | 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](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/configure-edge-synchronization.md). ## 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 * Use [Node status and health](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/node-status-and-health.md) to interpret the result. * Use [Update EVE-OS on nodes](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/update-eve-os-on-nodes.md) for single-node EVE-OS updates. * Use [Configuration locking](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/configuration-locking.md) if expected configuration changes are queued.