New in ZEDEDA Cloud Release 15.5
Article publish date: (5/5/2025)
ZEDEDA Cloud versions
- ZEDEDA GUI: 15.5.4
- ZEDEDA API: 15.5.7
New features
- The Onboard an Edge Node wizard helps you onboard a single edge node to ZEDEDA Cloud. The single page layout is revised to a more intuitive wizard layout to guide you through:
- Selecting a model now automatically imports the model from the global marketplace.
- Providing you with a pre-populated onboarding key and a default network configuration.
- Creating a new network without leaving the wizard.
- Creating a project without leaving the wizard.
- Docker Compose support (Early Access):
- Introduces the ability to define and manage multi-container edge apps using Docker Compose. You can manage multiple Docker containers as a single service using a plain text compose.yaml file, or a tar file for more complex setups that have multiple files. This simplifies the deployment and orchestration of complex edge applications consisting of several interconnected containers.
- This feature requires EVE-OS version 14.5.0-LTS or greater. Please contact ZEDEDA to participate while in Early Access.
- The Edge App Type Creation layout is separated into multiple tabs for efficiency, clarity, and consistency. Changes include items such as renaming the Environment to Interface to better reflect their purpose.
- Edge AI: Nvidia Jetson enhancements
- Pre-built EVE-OS container images for supported arm64 and Jetson platforms are now available from the dockerhub EVE repository.
- Support for Orin AGX dev board
- Support for Aetina Orin AGX device
- OEM Hardware License Propagation:
- Hardware devices may come with an embedded Windows OEM license as part of their UEFI/BIOS firmware. This license is typically used when Windows is installed directly on the hardware. If the licensing terms permit using the license for a virtual machine on the same node, license propagation can now be enabled within the application definition. See Configure the Resources and Drives in Add a Virtual Machine as an Edge App Type.
- This feature requires EVE-OS version 14.5.0-LTS or greater.
- VLAN support for management interfaces and Local Network Instances:
- Virtual Local Area Networks (VLANs) enable the segmentation of a physical edge node port into multiple logical networks. Prior to this enhancement, VLAN support was provided for applications connected on switch network instances only (through VLAN configuration at the app interface level). This enhancement extends VLAN support to management interfaces and local network instances. For these use cases, one or more VLANs can now be created at the edge node adapter level. See:
- This feature requires EVE-OS version 14.5.0-LTS or greater.
- New menu action item for Create Snapshot in the Edge App Instances page, if the device has the capability. With this new menu action, you can take backups even if air-gapped or offline for long periods of time. This feature requires EVE-OS version 14.5.0-LTS or greater.
Enhanced features
- Deployment project enhancements:
- Terraform support for deployment projects.
- You can now add a new deployment from the Administration > Projects > Deployments tab after you have deleted all your deployments from the project. Prior to this release, it wasn’t possible to create a new deployment from this location after deleting all of them.
- Version numbers are no longer automatically added to deployment policy names.
-
USB adapter type is now compatible with the USB Controller and USB Device adapter types for configuring passthrough devices. For example, when configuring direct attach for an edge app.
- This feature requires EVE-OS version 14.5.0-LTS or greater.
-
Network configuration enhancements:
- The current ipv4/ipv6 options have been renamed to Dual-stack IPv4 preferred and Dual-stack IPv6 preferred to correctly describe their behavior.
- The ability to select IPv4 Only or IPv6 Only has been added.
- This requires EVE-OS version 14.5.0-LTS or greater.
- The REST API endpoint for /v1/apps/images can now return multiple image types:
- IMAGE_TYPE_APPLICATION
- IMAGE_TYPE_EVE
- IMAGE_TYPE_ZKS_RUNTIME
- IMAGE_TYPE_DOCKER_RUNTIME
- IMAGE_TYPE_ARTIFACT
- IMAGE_TYPE_DOCKER_COMPOSE_TAR
- IMAGE_TYPE_EVEPRIVATE
- IMAGE_TYPE_UNSPECIFIED
- You can use the ZCLI or API to create a new edge node and activate it in the same API call.
Fixes (resolutions to customer reported bugs)
- In Marketplace > Models > Attestation, when no PCR templates are added, an empty screen is now displayed, and the Filter and ellipsis (...) icons are disabled.
- In Marketplace > Edge Apps > Global Edge Apps, the Import button is fixed.
- In Library > Volume Instances > Basic Info, the link to the Content Tree is fixed.
- Alert notifications are updated with a new look and feel.
- The suspended account error message of “Could not contact server. Please try again later.” has been changed to “Your account has been locked due to multiple failed attempts."
- While offboarding and onboarding a gateway with new tags, the new tag values are now updated in ZEDEDA GUI and also in the API response of /api/v1/devices/status.
Known issues
- Onboarding an edge node with a network instance of type IPV4 only will fail.
- Docker Runtime in the ZEDEDA GUI should be named Compose Runtime. This is being addressed in the next release, but the Help Center articles are ahead of the GUI renaming.
- After you create a Compose runtime edge app, the ZEDEDA GUI does not display the zrun image in the Edge App Image field when you edit the Compose runtime edge app in the ZEDEDA Marketplace.
- The fields of Enable CPU Pinning and VNC Connection located in the edge app Drawer component on the Edge App Instances page are not applicable for Docker Compose applications.
- When you create a virtual machine for a Compose runtime app, the Runtime Version and Runtime Protocol Version fields are not configurable in the edge app creation page.
- In a Docker Compose app instance the storage is shown as empty in the ZEDEDA GUI. The storage information should display amounts for total, used, and allocated.
- The Docker Compose container run status is incorrectly shown as 'online' even when the device is in a running, halted, or other state.
- In a Docker Compose app instance error messages are displayed in the run state for 3-6 minutes when upgrading the runtime, restarting the runtime, or restarting the edge node. Workaround: wait a few minutes and the error will clear.
- Docker Compose - Use standard base64 encoding for validation. With some Yaml files, ZEDEDA Cloud may return “Invalid base64 data” at the creation time for the Docker Compose app bundles. Workaround: Create a tar image file containing the affected compose.yaml file, and then create your app with the tar file.