Release 17.6

Updated

Article Published Date: 11/4/2025

ZEDEDA Cloud versions

  • ZEDEDA GUI: 17.6.6
  • ZEDEDA API: 17.6.7

New GA Features

ZEDEDA Edge Kubernetes Service and ZEDEDA Edge Kubernetes App Flows

The ZEDEDA EDGE Kubernetes Solution extends the power of VM and container orchestration to resource-constrained edge devices. 

  • This platform-native implementation enables the deployment, scaling, and management of applications across diverse edge locations. 
  • It leverages open-source Kubernetes' extensible architecture and adapts it for edge environments, providing a robust, scalable, and user-friendly platform that addresses the unique challenges of edge computing.
  • A new top-level menu in the GUI, Edge Kubernetes, is introduced to support the new  functionality.
  • This feature requires EVE-k v16.0.0 or greater.
  • Note that ZEDEDA Edge Kubernetes Service and App Flows is a commercial capability. Contact ZEDEDA sales representative for more details.
  • Terraform Provider support is a work in progress. 

ZEDEDA Flash Support

Introducing ZEDEDA Flash for Mac, Windows, and Linux. This new utility simplifies the process of flashing EVE-OS images to a USB drive or an SD card during the process of onboarding edge nodes as described in Flash an EVE-OS installer or live image. The ZEDEDA Flash UI streamlines the initial steps by providing a user interface that reduces configuration errors to ensure consistency. ZEDEDA Flash includes safety features, such as system drive protection, to prevent accidentally flashing of your laptop’s main drive. Other key features include:

  • Easily choose EVE-OS LTS images directly from our official GitHub repository.
    • Support for AMD64, (generic) ARM64 and Nvidia Jetson (JP5/JP6) images
    • Local caching of downloaded images
  • Support for common file formats such as .raw, .img, .wic, .zip, .gz, .xz, .iso, and .zst for generic flashing needs

Edge Sync UI

The existing Edge-Sync provides a solution for air-gapped environments allowing control over a fleet of EVE devices through an intermediary system, which is the Edge Sync server. You can now use the new Edge Sync UI to interact with your Edge Sync instance (in addition to the existing API interactions). You can use the Edge Sync UI to observe status information for troubleshooting, also to apply a new EVE-OS config for upgrading the application stack. Note that Edge Sync UI is a commercial capability. Contact ZEDEDA sales representative for more details.

Edge Node Cluster three-node or two-node with tie-breaker

The Edge Node Cluster feature now is GA and also has two configuration options. You can configure the original three-node high availability (HA) or you can configure two-node HA with one extra node local tie-breaker. 

Enhanced GA Features

Docker Compose enhancements

This release adds several key improvements for Docker Compose.

  • Improved Customization:
  • Bulk Deployments - Deploy Docker Compose runtime and app for multiple nodes & policies: 

Static IP - adapter specific

During Edge Node Onboarding, you no longer have to create specific Network objects per static IP address. You now have the option to reduce the number of static Network objects in your enterprise by creating a general adapter-specific network, which allows you to manually enter IP details on-the-fly rather than choosing from pre-configured options.

Disable vTPM

vTPM is enabled by default for newly-created edge apps of type VM, but now you can disable vTPM during initial VM creation if it is not required (such as for key generation, attestation, and sealed storage in environments without a physical TPM device) or for compatibility issues with legacy applications. 

Note that if you edit an existing Marketplace > Edge App to disable vTPM, and then propagate the updated config out to your Edge App Instances, it is a condition that will trigger a Purge & Update. It is a destructive action. For example, if you use Windows Bitlocker and update your Edge App Instance to disable vTPM, you will lose all your Bitlocker keys.  

Add VLAN sub-interface directly to a Switch Network Instance

You can now add a VLAN sub-interface directly to a Switch Network Instance: 

Local network reconfiguration

From the existing Edge Nodes > NODE_NAME > Adapters tab, you can now enable Allow modifications locally (LPS) to permit local management of network port configuration with Local Profile Server so that you can do the following:  

  • Reconfigure IP while disconnected from ZEDEDA Cloud.
  • Reconfigure IP by an (onsite) operator that doesn’t have ZEDEDA Cloud access.
  • This feature requires EVE-OS version 14.5.2-LTS or greater.

Single-use installer advanced configuration

As part of the edge node onboarding flow, you can generate a single-use installer now with EVE-OS and application storage on a single drive of your choice or you can specify EVE-OS & application storage disks on separate drives of your choice. To use this option, you must know the exact name of your Installation Disk (such as sda) or Storage Disk (such as sdb).

Retrieve onboarding details later 

In the edge node onboarding workflow, the Retrieve Onboarding details later option is now removed from the Hardware Identity drop-down. This GUI change reflects a backend change that had already been removed.

Clear session

The Clear Session link is added to Edge Node > Remote Access > Access Application tab so that you can clear an existing VNC session. For SSH, you can close terminal window to clear the session.

New Early Access Features

ServiceGraph Connector for ServiceNow Integration (Beta) 

This release introduces the ZEDEDA ServiceGraph Connector for ServiceNow, a new integration developed by ZEDEDA. The connector continuously synchronizes critical data (hardware details, location, status) from your ZEDEDA-managed edge nodes directly into the ServiceNow Configuration Management Database (CMDB), ServiceNow's “system of record” for IT & OT assets. This integration allows you to view and manage your edge nodes and OT assets directly alongside your traditional corporate servers and laptops within the ServiceNow platform. For example, you can automatically create incident tickets for edge node failures or leverage ServiceNow’s native workflows to streamline field service operations. 

  • Please contact your sales rep to get engaged on the early access list to provide feedback. 
  • This feature will be general available (GA) in H12026 release

Known Issues

  • To have the collect-info feature working correctly with Edge Sync, the datastore configured on the edge node must support POST API calls to create resources. If it does not, the collect-info upload will fail. The current EVE-OS implementation does not dynamically adjust the upload mechanism based on the server’s supported capabilities. ​​If you are using third-party HTTP servers or your own datastore setups, which don’t natively support POST, for Edge Sync you need to ensure that additional configurations are applied to handle POST (such as enabling WebDAV or adding a custom handler script) for the collect-info functionality to work correctly.
  • Docker: [ENG-2084] Compose App Instance will create a job that shows 'the requested job does not have any individual tasks' for a few minutes before generating the run status.
  • ZEDEDA Edge Kubernetes App Flows: [ENG-2154] Downloading kubeconfig from the cluster dashboard always provides read-only access to kubectl.
  • ZEDEDA Edge Kubernetes App Flows: [ENG-2051] When attempting to update a resource in a cluster via the cluster dashboard > import YAML option, 500 internal server errors are encountered due to permission restrictions for shadow users in the default namespace.
  • ZEDEDA Edge Kubernetes App Flows: [ENG-2151] When configuring an app repo of type HTTP(S) under Edge Kubernetes > Kubernetes Marketplace, the icon for the HTTP(S) repo is the GitHub icon.

Other News

EVE-k

EVE-Kubevirt, introduced as early-access in 14.5.0, is being renamed to EVE-k. For example, image names will change from X.Y.Z*-kubevirt-amd64 to X.Y.Z*-k-amd64. EVE-k is a k3s-based EVE-OS variant that enables edge-node clustering and ZEDEDA Edge Kubernetes Service. The standard EVE-OS variant is unchanged and remains the recommended option for deployments not using these capabilities. This is not a cloud feature, though certain cloud features in this release depend on future EVE-k functionality. EVE-k will be generally available in v16.0.0 in November.

  • For installation, we recommend all the edge nodes be of the same hardware type/model with a minimum of 12 core CPUs, 16 GB RAM, and NVMe SSDs for EVE persistent storage for optimal performance. 
  • For runtime, EVE-k consumes approximately 4 GB of memory and 2 vCPUs if used for clustering.
  • It recommended, though not strictly required, to separate the management traffic from the cluster traffic.
Was this article helpful?
0 out of 0 found this helpful