Version: v3.8.0

Upgrade and rollback

potctl upgrades Edgelet nodes to the version the Controller expects and can roll back to the previous release on the host.

Platform train v3.8.0 requires Edgelet v1.0.0+. Greenfield migrations need new nodes, not in-place Agent upgrades. See Migrating to v3.8.0.

Upgrade from the orchestrator

potctl upgrade agent zebra-1

The node downloads and applies the target Edgelet release. Upgrade can take several minutes.

Verify version:

potctl get agents
potctl describe agent zebra-1

If the version does not change, check logs on the host:

sudo journalctl -u edgelet -n 100 --no-pager
tail -f /var/log/edgelet/daemon-startup.log

potctl rollback agent zebra-1

Rollback uses the previous release recorded on the node during the last successful upgrade.

Fleet upgrades on linux use two layers (thin binary + fat embed). Operators may also run:

sudo sh /usr/share/edgelet/install.sh --upgrade --version=v1.0.0
sudo sh /usr/share/edgelet/install.sh --rollback

See Edgelet installation for airgap, controller-driven OTA, and runtime split restart order.

Action	Typical workload impact
Thin binary upgrade	Brief control-plane restart; MS may survive with runtime split
Fat bundle upgrade	Restart `edgelet-containerd` then `edgelet`; reconcile recreates MS
`rollback agent`	Same as upgrade path in reverse

See Workload continuity for embedded engine restart ordering.