Edgelet
Platform train v3.8.0 requires Edgelet v1.0.0+ on every Edgelet node. The legacy iofog-agent is not supported. See Migrating to v3.8.0.
Edgelet is the node runtime for Datasance PoT v3.8. It runs container workloads on edge hardware and reports to the Controller. In YAML you still use kind: Agent; in UI prose we say Edgelet node.
Pair Edgelet v1.0.0 with Controller v3.8.0 on the same release train.
What is an Edgelet node?â
On linux, production uses a two-layer binary:
| Layer | Path | Role |
|---|---|---|
| Thin | /usr/local/bin/edgelet | OTA binary, operator CLI, edgelet deploy client |
| Fat | /var/lib/edgelet/data/current/bin/edgelet | Daemon: supervisor, field agent, process manager, EdgeletAPI, embedded containerd |
Operator CLI commands talk to EdgeletAPI on localhost. The field agent talks to the remote Controller over HTTPS.
Two APIs on one nodeâ
| API | Base path | Purpose |
|---|---|---|
| Controller REST | {controllerUrl}/api/v3/... | Fleet sync: microservices, registries, status, OTA |
| EdgeletAPI v1 | https://127.0.0.1:54321/v1/... | Local admin: deploy manifests, edgelet ms, exec, prune |
Do not confuse them. The edgelet CLI is an EdgeletAPI client, not a Controller client.
Two workload sourcesâ
| Source | How it arrives | Typical use |
|---|---|---|
| Controller sync | Field agent polls changes, writes SQLite, process manager reconciles | Production fleet from potctl |
| Local deploy | edgelet deploy -f manifest.yaml via EdgeletAPI | Lab manifests, registries, RuntimeClass, optional ControlPlane |
Local manifests use apiVersion: edgelet.iofog.org/v1. See Deploy manifests.
Documentation mapâ
Install and operateâ
| Document | Description |
|---|---|
| Edgelet node management | Day-2 fleet ops via potctl (config, attach, prune, upgrade) |
| Architecture | Module layout, thin/fat binary, data flows |
| Installation | install.sh, OTA, upgrade/rollback |
| Configuration | Profiles, init-config, common defaults |
| Configuration reference | Every config key and reload behavior |
| Deployment | Production topology, engines, systemd |
| Troubleshooting | Daemon, cgroup, auth, exec |
Workloads and runtimeâ
| Document | Description |
|---|---|
| Deploy manifests | Microservice, Registry, RuntimeClass, ControlPlane YAML |
| Container engines | edgelet, docker, podman, RuntimeClass |
| Wasm runtime | Wasm handlers and RuntimeClass |
| DNS & discovery | svc.bridge.local, bridge aliases |
| Volumes | VOLUME persistence and prune |
| Workload continuity | Restart control vs data plane |
Local Controller and APIâ
| Document | Description |
|---|---|
| Control plane on node | Optional kind: ControlPlane manifest |
| ControlPlane runtime | Reconcile and DNS for local Controller |
| EdgeletAPI v1 | On-device REST/WebSocket API |
| Exec sessions | Multi-session WebSocket exec |
Data and logsâ
| Document | Description |
|---|---|
| Persistence | SQLite backup, restore, wipe-only upgrade |
| Logging | Structured events and journald queries |
CLIâ
| Resource | Path |
|---|---|
| CLI overview | CLI Reference |
| Root command | edgelet |
Per-command pages are autogenerated in the sidebar.
Legacy Agentâ
For the deprecated Java ioFog Agent and Agent-Go, see Legacy Agent (v3.7) and the v3.7.3 snapshot.
See alsoâ
- Setup Edgelet Nodes - orchestrator workflow with potctl
- YAML Reference: Agent -
kind: Agentfields for Edgelet nodes