Skip to main content
Version: v3.9.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.9.0 requires Edgelet v1.1.0+ on every node.

Upgrade from the orchestrator​

potctl upgrade agent zebra-1

Optional target pin:

potctl upgrade agent zebra-1 --semver {{EDGELET_VERSION}}

The Controller schedules an asynchronous upgrade on the node. Poll status with describe agent (isReadyToUpgrade, version fields). Upgrade can take several minutes.

Verify:

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

Upgrade vs redeploy​

PathWhen to use
upgrade agentNode already enrolled; Controller-driven OTA to the expected train version
deploy -f with new spec.package.version or imageRe-run bootstrap install path (for example major jump, broken OTA, or host repair)

Greenfield migration from legacy Java Agent to Edgelet requires new nodes, not in-place upgrade. See Migrating to v3.8.0.

Rollback from the orchestrator​

potctl rollback agent zebra-1

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

On-host OTA (linux)​

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

sudo sh /usr/share/edgelet/install.sh --upgrade --version=v{EDGELET_VERSION}
sudo sh /usr/share/edgelet/install.sh --rollback

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

Workload impact​

ActionTypical workload impact
Thin binary upgradeBrief control-plane restart; MS may survive with runtime split
Fat bundle upgradeRestart edgelet-containerd then edgelet; reconcile recreates MS
rollback agentSame as upgrade path in reverse

See Workload continuity for embedded engine restart ordering.

See also​

Group 3See anything wrong with the document? Help us improve it!