Izuma Edge 2.7.0 - August 2026

Documentation

• New chapter: Deploy a workload to a group of gateways.
  • How to group gateways with node labels, and how membership changes as gateways join and leave.
  • How to target a group with a DaemonSet rather than deploying to one gateway at a time.
  • How to read the rollout counters, in the Izuma Device Management Portal and with kubectl rollout status.
  • How to diagnose a gateway in the group that does not come up, including the symptoms specific to an intermittently connected fleet.
• Deploying containerized applications remains the starting point for a single gateway, and for creating the access key and kubeconfig file that both chapters need.

Known issues

• Kubernetes and pelion-edge-provisioner do not work on intel-corei7-64 on QEMU.
• Alpine Linux/muslc has issues with DNS lookups when used from containers. For more details, see Deploying Containers/DNS issues.
• The new golang- based terminal has some stability issues that can lead to connection loss. Click Reopen Terminal to reconnect.
• Izuma Device Management portal is not correctly updated after a firmware campaign in some instances.
• [Maestro] The FeatureMgmt config resource is initialized with a maximum file content of 3.8KB. The remaining file content is truncated during initialization. This is most likely due to the limitation of the Gorilla WebSocket library but needs further investigation. However, you can still push a file of up to 64KB through cloud service APIs.
• [pt-example] cpu-temperature device reports random values because the default CPU temperature file is not the same on Yocto and LmP.
• When using the Notification service API, if you subscribe to a translated device's LwM2M resources, which are registered with operation write (PUT) or execute (POST), you will not receive notification of the device state change.
• When using Wi-Fi, the device shutdown can take longer than expected because Edge Core takes 1m 35s to shut down.

Limitations

• There is a maximum size limit to the full registration message, which limits the number of devices Izuma Edge can host:
  • Maximum registration message size is 64KB.
  • Hosted devices with five typical Resources consume ~280B (the exact size depends, for example, on the length of resource paths). This limits the maximum number to 270 devices.
  • The more Resources you have, the fewer devices can be supported.
  • Izuma Edge device Resources are also included in the same registration message.
  • Test the limits with your configuration and set guidance accordingly.
• Devices behind Izuma Edge do not support auto-observation.
• Izuma Device Management Client-enabled devices must bootstrap to the Izuma Device Management cloud before connecting to Izuma Edge.
• No moving devices are supported (such as the device moving from Izuma Edge to another edge device).