Reading notes from 2022; revised November 17, 2026. Reported architecture and scale refer to the source period.

Disconnection is an architectural requirement

Baetyl, KubeEdge, and OpenYurt connect cloud management with edge execution, but a list of components does not establish equivalent behavior. Compare them around what happens when the link disappears.

Scenario What a comparison should establish
Cloud link fails Which workloads continue and which operations block?
Device changes state Where is the latest observation stored?
Cloud and edge both change Which desired state wins after reconnect?
Update is interrupted Can the node resume or roll back?
Credentials expire offline Which capabilities remain available?

Follow desired and observed state

A cloud control plane expresses desired application state. The edge observes devices and local workload health. Those views can diverge during an outage. Reconciliation needs identity, versioning, and a conflict policy; simply reconnecting does not establish that the newest or safest state wins.

For an illustrative test, deploy a small workload, disconnect the management link, restart the node, modify desired state, then reconnect. Observe whether the workload continues, how status is buffered, and which change is applied. These are proposed test cases, not claimed results for all three projects.

Choose from operational constraints

Compare device protocols, local storage, footprint, upgrade process, and identity boundaries using release-specific documentation. The historical component diagrams in the repositories may move or describe a different version; the original conceptual flow below avoids depending on those remote images.

Comparing Cloud Edge Reconciliation Designs

Conceptual illustration; labels describe responsibilities, not a deployment specification.

References