Release 21.2.6

Updated

Article Published Date: 11/3/2026

ZEDEDA Cloud versions

  • ZEDEDA API: 21.2.6 (upgrade from 20.0.20)
  • ZEDEDA GUI (classic): 21.1.5
  • ZEDEDA UI Console (new): 1.2.16

Release 21.2.6 lets you add or remove network interfaces on running application instances without redeploying them, attach persistent data disks to Docker Compose runtimes, and introduces two-node high-availability clusters with a witness. It also makes large Terraform-driven deployments reliable at high parallelism, tightens API input validation, and resolves more than 40 issues.

Review Changed Behavior and Known Issues before upgrading automation, scripts, or Terraform configurations. Several API calls that previously succeeded silently now return HTTP 400.

Feature Minimum EVE-OS version
Network interface changes on running application instances The upcoming EVE-OS 18.x LTS. On earlier versions, the edge node does not apply the change.
Persistent data disks for Docker Compose runtimes EVE-OS 14.5.0 LTS on edge nodes with ext4 persistent storage. A 16.0.x LTS release on edge nodes with ZFS persistent storage.

New Features

Change network interfaces on running application instances

New UI console only. You can now add, remove, or swap network interfaces on a deployed VM or container application instance without deleting and redeploying it. You can also move an interface to a different network instance and update its ACL rules in place. Adding, removing, or swapping an interface triggers one automatic restart of the application; the instance's volumes are preserved. Requires the upcoming EVE-OS 18.x LTS on the edge node.

See the following in the new documentation site:

SMT-aware CPU placement

New UI console only. CPU placement now accounts for symmetric multithreading (SMT) sibling relationships when assigning vCPUs to physical cores. On edge nodes with hyperthreading enabled, you can choose whether a workload uses one thread per core or both SMT threads of each reserved core, so that performance-critical vCPUs are not placed on logical threads that share a physical core with other workloads. This removes cache and execution-unit contention between pinned vCPUs and gives more predictable latency and throughput for latency-sensitive workloads such as SD-WAN routing, IPsec encryption, and high-frequency data processing. CPU placement applies to VM and container applications on EVE-KVM edge nodes that report a CPU topology.

See CPU Placement for Application Instances in the new documentation site.

Persistent data disks for Docker Compose runtimes

Classic GUI and new UI console. A Docker Compose runtime edge app can now declare extra data disks after its boot image. A data disk is either a blank persistent disk owned by the instance, or an existing volume instance attached by its volume label. A labeled volume survives deletion of the runtime instance and reattaches to a new instance, so you can move workloads from other runtimes without copying data. Requires EVE-OS 14.5.0 LTS, or a 16.0.x LTS release on edge nodes with ZFS persistent storage.

See the following:

Two-node high-availability clusters with a witness

You can create a two-node HA edge node cluster backed by an etcd witness on the seed node, or convert a single-node cluster to two-node HA. If the seed node fails permanently, a quorum reset promotes the surviving node and keeps the cluster running on a single node until you add a replacement. Two-node HA is available in the new UI console, the API, and ZCLI.

Enhancements

Unified clusters

New UI console only. Edge Node Clusters and ZEDEDA Edge Kubernetes Service clusters are now a single cluster type. Every cluster runs application instances (VMs, containers, and Docker Compose workloads) with Longhorn storage and KubeVirt on each edge node. When you create a cluster, or later on its detail page, you can enable Kubernetes access to add kubectl, GitOps, Helm, the Kubernetes dashboard, and a cluster shell. Enabling Kubernetes access on a running cluster is non-destructive: existing application instances and storage stay online. You can also import an external Kubernetes cluster for GitOps and Helm delivery without ZEDEDA edge nodes.

The cluster list at Infrastructure > Fleet > Clusters shows every cluster type in one view. Each entry shows a Mode badge (Edge Node Cluster, K8s Cluster, or Imported K8s Cluster), and all cluster types are managed through the /api/v1/cluster endpoints.

EVE-OS update history

Each edge node now keeps a history of its EVE-OS image updates, available through the API.

Bulk refresh and purge by project or device list

Bulk application instance refresh and purge no longer require an edge app. You can target a whole project, or narrow the selection with a device list. Instances that are already up to date are reported as not required instead of failing the job.

Docker Compose runtime deactivation

A Docker Compose runtime can now be deactivated after all of its Compose app instances are halted. Deleting the runtime still requires removing the Compose app instances first.

More application instances per edge node

Application instances whose edge app has VNC disabled no longer consume a VNC display slot. This removes the previous limit of 63 application instances per edge node.

API additions

  • The device and application instance status-config list endpoints support sorting by field.
  • The Users API stores new UI console preferences (cortexSettingsCustom).
  • Network instances on edge node clusters are marked as cluster-wide in the edge node's configuration.

User interface updates

  • New UI console only. The application instance remote console now uses Edge View.
  • Application and edge node port fields are validated in the UI. A port must be less than 65535.
  • The classic UI login page shows an announcement about the new UI console.

Terraform

The zedcloud_auth_profile resource now works with OAuth authorization profiles, including create and terraform import.

Changed Behavior

Review the following changes before upgrading automation, scripts, or Terraform configurations. Entries are ordered by likely impact.

Area Before 21.2.6 From 21.2.6 What to do
API list filters An unrecognized value for imageArch, imageStatus, imageType, imageTypes, appType, originType, or project type was ignored and the full list was returned. Some valid values were also ignored. Values are matched case-insensitively. An unrecognized value returns HTTP 400. Valid filters now filter, so results can be shorter. Check scripts that pass these filters.
Volume instances An invalid access mode could be stored. Changing the access mode on update returned HTTP 200 but did nothing. Invalid access modes are rejected with HTTP 400. Changing the access mode after create returns HTTP 400. Sending the unchanged value still works. Set the access mode at create time only.
Volume instances Block storage volumes backed by a content tree could be created with size 0. Explicitly created block storage volumes need a non-zero sizeBytes. Setting it to 0 on update returns HTTP 400. Volumes created implicitly from app manifests are unaffected. Always pass sizeBytes for block storage.
Application instance interfaces A changed interface set was sent to the edge node but applied only after a manual restart. Adding, removing, or swapping an interface triggers one automatic restart. Rebinding an interface or changing only its ACL rules does not restart. Plan interface changes for a maintenance window where a restart is acceptable.
ACLs (projects with Interface Ordering) Edge app ACLs were appended to the instance's ACLs on create, update, and refresh. Edge app ACLs are defaults. A non-empty instance ACL list is stored as sent, and refresh no longer rewrites instance ACLs from the edge app. Projects without Interface Ordering keep the previous behavior. Push ACL changes to existing instances explicitly instead of relying on refresh.
Edge apps Renaming interfaces or toggling direct attach was allowed but broke later refreshes. These edits are rejected while instances use the edge app. Duplicate interface names in app policies are rejected. Create a new edge app version for these changes.
Bulk refresh and purge deviceIdList was ignored. A selection without an edge app failed. deviceIdList now narrows the selection. An empty selection completes as a no-op. Check that bulk jobs that pass deviceIdList target what you expect.
EVE-OS images Operators and admins could edit EVE-OS images through the general image update API. Updates to EVE-OS images through that API are rejected. Use the EVE-OS image workflows instead.
ZEDEDA Edge Kubernetes Service secrets Git and Helm repository credentials could be read back through the secrets API. Credentials are write-only. List responses do not include secret values. Detail responses mask private keys and passwords as ***. Results include only projects the caller can access. Keep credentials in your own secret store. Do not read them back from the API.
Cluster and user deletion Deletion ran synchronously. Deletion runs in the background. The API returns first, and the cluster shows a deleting state until the work finishes. Poll the status instead of assuming deletion is complete when the call returns.
Edge node debug mode Any edge node update, even a no-op, switched debug mode off. Debug mode changes only through the debug enable and disable calls. A debugKnob value in an update body is ignored. Use the debug enable and disable calls.
VNC Every application instance received a VNC display number. Instances whose edge app has VNC disabled receive no display number and report vncDisplay 0. No action required unless tooling relies on that number.
App profiles Moving an edge node between projects left its old profile membership in place. The edge node's applications from the old project's profiles are undeployed, and the new project's profiles are deployed. Expect application changes when moving edge nodes between projects.
Metrics API MEMORY_TOTAL was accepted as a time-series metric type but always failed. MEMORY_TOTAL is no longer a valid metric type. Remove it from metric queries.
OpenAPI specification OAUTHProfile.additionalParameters and Role.projectTags were described as strings. Both are described as string-to-string maps (JSON objects), which is what the API already returned. Regenerate API clients built from the specification.
Remote attestation Quotes were checked against all reported PCR values. Only PCR values covered by the TPM signature count, and a quote must answer an outstanding nonce. No action required for standard EVE-OS edge nodes. Contact support if an edge node stops attesting after the upgrade.
High-parallelism writes Bursts of application instance writes could exhaust capacity and fail. Writes are queued, so very large bursts complete, but individual calls can take longer. Check client timeouts for large Terraform runs.
Remote console The application instance remote console used the previous console path and an older console engine. The remote console uses Edge View on an updated console engine. Edge View must be reachable for the edge node.
Docker Compose runtimes Runtime instances accepted drives in the create request, and every runtime edge app version bump forced a purge. Drives for runtime instances come only from the edge app, and supplied drives are rejected. While instances exist, data disks can be added or removed only at the end of the edge app's drive list. An edge app bump that changes nothing no longer purges. Define data disks in the edge app and append new ones at the end.
ZEDEDA Edge Kubernetes Service API routes The /api/v1/zks/instances endpoints returned data normally. All legacy routes still respond but return Deprecation: true and Sunset: 2026-12-01 headers. Migrate to the /api/v1/cluster endpoints before December 1, 2026.
Edge node cluster size A cluster required exactly three edge nodes. The three-node minimum is removed. Single-node clusters are supported, and two-node clusters are supported with two-node HA. At most three edge nodes act as control-plane members; additional edge nodes join as workers. Update runbooks or automation that enforces a three-node count.
Enabling Kubernetes on an existing cluster Enabling Kubernetes on a running cluster removed storage and disrupted workloads. Enabling Kubernetes access is non-destructive. Existing application instances and storage remain online. Requires a recent EVE-OS build on the edge nodes. Verify edge node builds before enabling Kubernetes access on existing clusters.

Fixed Issues

Application instances at scale

  • Bulk create, update, and delete of VM application instances at high Terraform parallelism (40 or more) no longer time out with HTTP 504 or leave instances behind, and no longer stall unrelated API calls.

Application instances

  • Deployments to an edge node no longer fail permanently after repeated deploy and undeploy cycles because VNC display slots leaked. Spurious "No free VNC port" errors during create bursts are fixed.
  • A removed and re-added network interface no longer shows the previous interface's IP address.
  • Editing or removing a default ACL rule in the deploy wizard no longer re-adds the original rule, which caused overlapping port maps when deploying a second instance of the same edge app. Duplicate port map entries are removed.
  • Updating interface ACLs or the network binding through the API is now applied. Previously, the request returned HTTP 200 without changing anything.
  • Creating a snapshot now returns the snapshot's ID and name.

Edge apps

  • Deleting an edge app while an instance or policy is being created no longer leaves references to the deleted app. Image deletion and app list operations are faster on large enterprises.

App profiles

  • An edge node that leaves a project and rejoins it now gets its profile applications redeployed.

Edge nodes

  • Editing an edge node no longer switches off debug mode.
  • Generating a single-use EVE-OS installer no longer fails intermittently with HTTP 500.

Edge node clusters

  • Replacing an edge node in a cluster no longer deletes or orphans application instances and volumes, and a replaced edge node can now be deleted.

Resource usage

  • Fewer online edge nodes are missing from the device resource usage report. See Known Issues for the remaining limitation.

Login

  • Users without TOTP can now enroll when Enforce TOTP is enabled, instead of being stuck in a loop.

Projects

  • Filtering the project list by type no longer returns HTTP 500, and the type filter now applies to project status endpoints. Getting a single project now returns the correct device count.

Filters

  • The originType filter on brands, models, images, datastores, and apps is now applied when you pass enum names such as ORIGIN_LOCAL.
  • Filtering edge nodes by a tag value that contains & now works.

PCR templates

  • Searching PCR templates with a space in the name pattern no longer returns HTTP 400, and the list returns a total count.

Metrics

  • The unsupported MEMORY_TOTAL time-series metric, which always failed, is removed.

ZEDEDA Edge Kubernetes Service

  • Deleted clusters no longer stay in a deleting state for hours, and stale cluster entries are cleaned up. User deletion on clusters is faster.
  • New clusters no longer show the state None, and ZEDEDA Edge Kubernetes Service errors return a meaningful message instead of a generic HTTP 500.
  • Clusters with many failing Git repositories no longer destabilize cluster management.

Security

  • Device authentication and remote attestation checks are hardened.
  • Kubernetes Git and Helm repository credentials are no longer returned in API responses or written to logs, and secret listing is limited to projects the user can access.
  • Operators and admins can no longer modify EVE-OS images through the general image update API.
  • Connections to Kubernetes management require TLS 1.2 or greater, and third-party dependencies with known CVEs are updated.

User interface

  • New UI console only. The console no longer freezes on the edge node detail screen.

Known Issues

  • Two-node HA status shows Unknown. A healthy two-node HA cluster that has not changed for 5 minutes is shown as Unknown. The cluster keeps working; only the reported status is wrong. A fix will follow in a point release.
  • Network interface changes on running instances require a newer EVE-OS. Until EVE-OS 18.x LTS is available, interface changes on running application instances are not applied by the edge node.
  • The resource usage report can still miss some online edge nodes. A small number of online edge nodes might not appear in the device resource usage report.
  • Application and edge node port limits are checked only in the UI. The API still accepts port numbers greater than 65535.
  • Snapshot API edge cases. A snapshot can be created on an instance that does not allow snapshots. Deleting or activating a missing snapshot returns HTTP 500 instead of 404.
  • App profile deployments are limited to nine application instances per edge node. Larger profile deployments do not complete.
Was this article helpful?
0 out of 0 found this helpful