RATATOSKRATATOSK
Sign in

Releases

AI-analyzed release notes for CNCF graduated and incubating projects.

Project: KubeEdgeClear ×
KubeEdgev1.23.1Provisioning & RuntimeJul 15, 2026

A feature and behavior release that adds Windows and device-management capabilities, changes edge database and node-querying behavior, and updates the Kubernetes dependency. Device status retrieval now uses the new DeviceStatus CRD.

Check if affected (1)

  • breakingThe DeviceStatus CRD for device status retrieval

    Applies if you use the DeviceStatus CRD.

    In v1.23.0, the status portion of the Device CRD was extracted into the DeviceStatus CRD. Older CRD versions remain backward compatible, but device status must now be retrieved from the new CRD.

Source
KubeEdgev1.21.2Provisioning & RuntimeJul 15, 2026

This release combines correctness fixes with changes to node-job behavior, operator capabilities, and command workflows. It introduces configuration updates for edge nodes, which are disabled by default and require an EdgeCore restart; no security advisories are identified.

Check if affected (6)

  • breakingThe v1alpha2 NodeUpgradeJob and ImagePrePullJob defaults

    Applies if you use NodeUpgradeJob or ImagePrePullJob.

    From v1.21, v1alpha2 NodeUpgradeJob and ImagePrePullJob node jobs are enabled by default.

  • breakingNode-job switching constraint

    Applies if you use NodeUpgradeJob or ImagePrePullJob.

    The NodeUpgradeJob and ImagePrePullJob node jobs cannot be switched between each other.

  • breakingThe taskManager node-job module, disabled by default

    Applies if EdgeCore is running.

    The taskManager node job is a disabled-by-default Beehive module in EdgeCore.

  • + 3 more on the release page

Plan ahead (1)

  • deprecatedThe v1alpha1 NodeUpgradeJob and ImagePrePullJob jobs, deprecated

    Applies if you use NodeUpgradeJob or ImagePrePullJob.

    The v1alpha1 NodeUpgradeJob and ImagePrePullJob node jobs will no longer be maintained.

Source
KubeEdgev1.23.0Provisioning & RuntimeMar 11, 2026

This release expands Windows and device-management support while changing edge database and node-query behavior. It also updates Kubernetes and changes how consumers retrieve device status through the DeviceStatus CRD.

Check if affected (1)

  • breakingDevice status moved to the DeviceStatus CRD

    Applies if you use the Device CRD.

    The status portion of the Device CRD is extracted into a separate DeviceStatus CRD in v1.23.0. Older versions of the CRD remain supported, but device status must now be retrieved from the DeviceStatus CRD.

Source
Browse by month