Edgelet node management
Prerequisite: ECN with Edgelet nodes
You need a working Edge Compute Network (ECN) with provisioned Edgelet nodes. If you have not deployed nodes yet, start with Platform Deployment and Setup Edgelet Nodes.
Once Edgelet nodes are registered with the Controller, you run day-to-day operations from the orchestrator with iofogctl. In YAML the resource kind is still Agent; in prose we say Edgelet node.
Platform train v3.9.3 pairs with Edgelet v1.1.3 on every node.
This section covers fleet operations. For how the Edgelet daemon works on the device, see Edgelet.
What you can manage
| Topic | Page | Typical command |
|---|---|---|
| Runtime settings pushed from Controller | Configuration updates | iofogctl deploy -f agent-config.yaml |
| Hardware attestation | EdgeGuard | iofogctl deploy -f agent-config.yaml |
| Move nodes between ECNs or namespaces | Attach and detach | iofogctl detach agent, iofogctl attach agent, iofogctl move agent |
| Push host directories to nodes | Volume distribution | iofogctl deploy -f volume.yaml |
| Reclaim disk on nodes | Image and disk pruning | iofogctl prune agent |
| Fleet Edgelet version changes | Upgrade and rollback | iofogctl upgrade agent, iofogctl rollback agent |
| Router/NATS platform on a node | Reconcile platform | iofogctl reconcile agent |
| Daemon logs and node debug shell | Debugging | iofogctl logs agent, iofogctl exec agent |
Orchestrator vs on-device changes
| Layer | Tool | Use when |
|---|---|---|
| Controller push | iofogctl + AgentConfig | Fleet-wide config from the control plane |
| On-device | edgelet config, edgelet provision | Break-glass or air-gapped node admin |
See Edgelet configuration and Configuration reference for on-device keys.
See also
- Edgelet nodes in Learn -
Agent,AgentConfig, andspec.configfields - iofogctl Getting Familiar - namespaces,
get,describe,logs - Edgelet installation - manual install and OTA on the host
See anything wrong with the document? Help us improve it!