Edgelet node YAML Specification
Edgelet nodes run on edge hosts and connect to the Controller so microservices can deploy locally. In YAML the resource kind stays Agent (remote SSH deploy) or LocalAgent (local container). Prose and UI labels use Edgelet node.
Deploy with iofogctl deploy -f agent.yaml. Update a running node with the AgentConfig kind (configuration updates) or Edgelet configuration on the device.
v3.8 requires Edgelet v1.0.0+ on every node. The Java ioFog Agent and v3.7 field agents are not supported. See Migrating to v3.8.0 and Legacy Agent (v3.7) for the v3.7.3 snapshot.
v3.8 field renames
| Legacy (v3.7) | v3.8 |
|---|---|
agentType | arch |
fogType / fogTypeId | arch / archId |
dockerUrl | containerEngineUrl |
dockerPruningFrequency | pruningFrequency |
| - | containerEngine: edgelet, docker, or podman |
Architectures: auto, amd64, arm64, riscv64, and arm (32-bit). Catalog and offline images use archId with the same four architecture names.
Default Edgelet image tag for the v3.8 release train: ghcr.io/eclipse-iofog/edgelet:1.0.0. Override under spec.package.container.image or spec.package.version for native binary installs.