> ## 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.

# Update EVE-OS with Release Manager

> Download, install, and monitor EVE-OS updates with Release Manager, targeting whole projects, node selections, or single nodes.

## Introduction

This procedure explains how to use Release Manager to update EVE-OS (Edge Virtualization Engine) on your nodes and clusters.

For individual nodes, the process has two stages: downloading the new EVE-OS image to the node's inactive partition (the secondary disk slot used for A/B updates, separate from the currently running partition), then installing it (which activates the image and reboots the node). You can run both stages together or separately to fit your maintenance schedule.

For clusters, the upgrade is always atomic and is not currently available in Release Manager. See [Upgrade a Cluster](#upgrade-a-cluster).

### Prerequisites

* You have the SysManager or SysAdmin role in your enterprise. See [Manage Roles](https://zededa.mintlify.site/new-ui/infrastructure-services/administration/manage-roles.md).
* At least one node with **Needs update** status in Release Manager.

## Open Release Manager

1. In the sidebar, click **Infrastructure > Operations > Release Manager**.
2. On the **Nodes** tab, wait for the fleet scan to complete. A loading indicator appears while Release Manager scans your nodes.

## Choose Your Update Scope

Release Manager supports three update scopes. Choose the one that fits your use case, then follow the corresponding section.

* **Update all nodes in a project**: Use the project row action menu or the project drill-down page. Targets every node in that project.
* **Update a selection of nodes**: Filter or search for the nodes you want, select them with checkboxes, then use the bulk action toolbar.
* **Update a single node**: Use the action menu on an individual node row.

## Choose a Target EVE-OS Version

Every Download, Install, and Download & Install dialog uses the same **Target EVE-OS Version** dropdown. The dropdown works as follows:

* **Published and uploaded images**: The list includes ZEDEDA's published EVE-OS catalog and any EVE-OS images your enterprise uploaded to the Library, for example with ZCLI. An uploaded image appears only after its status is ready and its name contains a recognizable EVE-OS version.
* **Compatible builds only**: When all target nodes share the same CPU architecture (AMD64 or ARM64) and EVE-OS flavor (KVM or EVE-K), the list shows only versions that have a build for that architecture and flavor. If the targets span more than one architecture or flavor, the list shows the full catalog. Nodes without a compatible build of the selected version are skipped, and the result reports them as skipped.
* **LTS filter**: Use the **All**, **LTS**, and **Non LTS** toggle above the dropdown to narrow the list to long-term-support releases or to release candidates and other non-LTS builds. If the selected version is hidden by the filter, the first version in the filtered list is selected instead. If no versions match, the dialog shows a message such as "No LTS versions available for these nodes."
* **Version order**: Versions are sorted newest first. An LTS release sorts above a release candidate of the same version.
* **Latest label**: The **(latest)** label marks the version that is marked as latest in the Library, not the first entry in the list. ZEDEDA Cloud keeps one latest mark per architecture. When the targets share one architecture, only that architecture's latest version is labeled. Otherwise, each label names its architecture, for example **(latest · AMD 64)** and **(latest · ARM 64)**.

## Update All Nodes in a Project

This operation targets every node in the project in a single job. Use it for fleet-wide rollouts or to update all nodes in one environment at a time.

### From the Nodes tab

1. On the **Nodes** tab, locate the project you want to update in the project table.
2. Hover over the project row to reveal the action menu (⋯) on the right side of the row.
3. Click the action menu and select **Download**, **Install**, or **Download & Install** (see [Understand the Download and Install Actions](#understand-the-download-and-install-actions) for the difference between each).
4. In the dialog that appears, select the target EVE-OS version from the **Target EVE-OS Version** dropdown. The latest published version is selected by default. To filter the list or learn which versions appear, see [Choose a Target EVE-OS Version](#choose-a-target-eve-os-version).
5. Review any warnings. A warning appears if nodes already have a different version staged (it will be replaced) or if the operation will reboot nodes and briefly interrupt running workloads.
6. Click **Download Now**, **Install Now**, or **Download & Install Now** to start the operation.

### From the Project Drill-Down

1. On the **Nodes** tab, click the project row to open the project drill-down page.
2. In the page header, click **Download**, **Install**, or **Download & Install**.
3. In the dialog, select the target EVE-OS version and review any warnings.
4. Click the confirm button to start the operation.

Edge Infrastructure Services submits a single project-scoped update job. You can track progress on the **Nodes** tab as node statuses update, or in **Infrastructure > Operations > Jobs**.

**Note:** If the project contains nodes with different CPU architectures, the update is dispatched per node instead of as one project job. A note in the dialog discloses this when it applies.

## Update a Selection of Nodes

Use this approach to update a specific set of nodes, for example nodes in a particular status or belonging to multiple projects.

### Select the nodes

1. On the **Nodes** tab, click a status chip (for example, **Needs update**) to filter the node list to nodes in that state. You can also search for a specific node name using the search field.
2. Hover over a node row to reveal its checkbox, then click it to select that node. To select all visible nodes, use the header checkbox.

### Run the update

1. The bulk action toolbar appears above the node table after you select nodes. Click **Download**, **Install**, or **Download & Install** (see [Understand the Download and Install Actions](#understand-the-download-and-install-actions) for the difference between each).
2. In the dialog, select the target EVE-OS version.
3. Review any warnings about staged versions or node reboots.
4. Click the confirm button to start the operation.

**Note:** The bulk toolbar only appears when every selected node belongs to a project where your role has device-write permission. If your selection spans projects where you lack permission on some, narrow the selection to nodes in projects where you have access.

## Update a Single Node

Use this approach to update one specific node, for example when testing a new EVE-OS version before a broader rollout.

1. On the **Nodes** tab, click a project row to open the project drill-down page.
2. In the node table, hover over the node you want to update to reveal its action menu (⋯).
3. Click the action menu and select **Download**, **Install**, or **Download & Install** (see [Understand the Download and Install Actions](#understand-the-download-and-install-actions) for the difference between each).
4. In the dialog, select the target EVE-OS version.
5. Review any warnings, then click the confirm button.

You can also reach a single node's action menu from the cross-project node view. Filter by a status chip, find the node in the list, and use its action menu. Click **Back** at the top of the project drill-down page to return to the **Nodes** tab.

## Upgrade a Cluster

Cluster-level EVE-OS upgrades are not currently available in Release Manager or on the cluster detail page. Use ZCLI to upgrade a cluster.

Clusters upgrade atomically. The upgrade downloads and activates the selected version across all member nodes as a single operation. You cannot separate the download and install steps for a cluster, and you cannot target individual member nodes.

To upgrade a cluster, run the following command:

```bash theme={"dark"}
zcli edge-node-cluster upgrade <name> --image=<eve-os-image>
```

To check the progress of the upgrade on each member node, run:

```bash theme={"dark"}
zcli edge-node-cluster show <name> --upgrade
```

## Understand the Download and Install Actions

**Note:** The Download, Install, and Download & Install actions apply to individual node operations on the **Nodes** tab. For clusters, see [Upgrade a Cluster](#upgrade-a-cluster).

**Download** stages a new EVE-OS image on the node's inactive disk partition. The node continues running on its current EVE-OS version. No reboot occurs. Download is the right choice when you want to pre-stage updates ahead of a maintenance window and activate them later.

**Install** activates an image that was previously downloaded. EVE-OS switches to the staged partition and reboots the node. The reboot briefly interrupts running workloads. Install is only available on nodes that already have a staged image.

**Download & Install** combines both steps. EVE-OS downloads the selected image and immediately activates it, rebooting the node. Use this when you want to update nodes in one operation and do not need to separate the staging and activation steps.

If you click **Install** but no image is staged on the target nodes, a dialog appears noting that no image is staged and offering to run **Download** or **Download & Install** instead.

## Monitor Update Progress

After starting an update, node statuses on the **Nodes** tab update live.

1. Nodes transition from **Needs update** to **Downloading**, then **Downloaded** (if you ran Download only), or directly from **Downloading** through the install sub-phases to **Up to date** (if you ran Download & Install). During the install, the status label advances through sub-phases: Verifying, Initializing, Rebooting, Booting, Testing, Needs Test Confirmation, Update Deferred, and Updating.
2. The status chips at the top of the page reflect the current fleet-wide counts.
3. If a node's update fails, a red triangle appears next to its status badge. Hover over it for the failed version, and click it to open the associated job for details.

## View Update History

The **History** tab shows the EVE-OS image history recorded for a single node. History is recorded per node, so you select a node before any events are shown.

1. On the Release Manager page, click the **History** tab.
2. In the node picker, select the node whose history you want to review. Until you select a node, the tab shows a prompt instead of a table.
3. The table lists each EVE-OS base-image event for that node with the following columns.
   * **Image Version**: The EVE-OS image version associated with the event.
   * **Action**: **Publish** (the version was staged on the node) or **Activate** (the version was applied and booted).
   * **Triggered By**: The user or system that initiated the event.
   * **Triggered At**: The timestamp of the event.
4. When the history is long, click **Load more** at the bottom of the table to page through additional entries.

Release Manager keeps the selected node in the page URL, so you can bookmark or share a link to a specific node's history. A node that has not yet received an EVE-OS update has no history and shows an empty state. Entries appear after an EVE-OS base image is published or activated on the node.

To review the outcome of update jobs, including per-node task results, open **Infrastructure > Operations > Jobs**.

## Next Steps

> [card] [Release Manager Overview](https://zededa.mintlify.site/new-ui/infrastructure-services/release-manager/release-manager.md)
>
> Background on update statuses and how the Nodes and History tabs work.

> [card] [Monitor Jobs](https://zededa.mintlify.site/new-ui/infrastructure-services/monitoring-logs-events-reports-jobs.md)
>
> Review detailed job results for completed update operations.