RATATOSKRATATOSK
Sign in

Releases

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

Severity
AllBreakingSecurity
Category
AllAI & MLCI/CD & App DeliveryKubernetes CoreNetworking & MessagingObservabilityOrchestration & ManagementProvisioning & RuntimeSecurityStorage & Data
Last 7 daysClear ×

KubeEdge

Provisioning & RuntimeJul 15, 2026
v1.23.1

KubeEdge v1.23.1 is a minor patch with one operator-facing breaking change: device status is now read from a new DeviceStatus CRD rather than the Device CRD status field. The release also adds Windows support, device anomaly detection, optimizes edge-to-cloud queries, and refactors the database backend to GORM.

  • breakingDevice status moved to DeviceStatus CRD

    Device status is now stored in a separate DeviceStatus CRD instead of in the Device CRD's status field. Code that reads device status must be updated to query the DeviceStatus CRD. Backward compatibility with older CRD versions is maintained, but the status field in Device is no longer the source of truth.

Key changes (7)
  • Device CRD restructured: status now lives in separate DeviceStatus CRD; queries must read from the new resource
  • Windows support added to EdgeCore and Keadm: named pipes, version mismatch detection, service log redirection
  • Device anomaly detection framework introduced via Device CRD pushMethod configuration
  • Edge node queries optimized to use local database instead of CloudCore remote calls
  • Edge database backend refactored from Beego ORM to GORM
  • Kubernetes dependency updated to v1.32.10
  • Dashboard v0.2.0: Backend-for-Frontend layer, Chinese language support, UI improvements
Source ↗

KubeEdge

Provisioning & RuntimeJul 15, 2026
v1.22.2

KubeEdge v1.22.2 is a feature release consolidating v1.22.1 bug fixes and v1.22.0 enhancements. Key additions include a hold/release mechanism for edge Pod updates, Beehive restart policy configuration, Device Model redesign, new feature gates for lightweight Kubelet control, a C-language Mapper-Framework variant, and a Kubernetes 1.31.12 dependency bump. No upgrade steps are required.

  • enhancementKubernetes dependency updated to v1.31.12

    Kubernetes has been bumped to v1.31.12; users can now use v1.31.12 features on both the cloud and edge sides. This change ships in v1.22.0 and applies to all deployments.

Key changes (7)
  • Kubernetes upgraded to v1.31.12, enabling new version features across cloud and edge
  • Hold/release mechanism for edge Pod updates via edge.kubeedge.io/hold-upgrade annotation and keadm ctl unhold-upgrade
  • Beehive framework now supports configurable restart policies for edge submodules
  • Device Model redesigned to integrate thing model and product concepts, with optional per-instance overrides
  • EdgeCore feature gates added for Pod Resources Server and CSI Plugin control
  • C-language Mapper-Framework introduced (feature-multilingual-mapper-c branch)
  • Three bug fixes: deviceInstanceConfig override in MapperRegister, policyManager reconciliation with non-cached reader, keadm reset edge container removal
Source ↗

KubeEdge

Provisioning & RuntimeJul 15, 2026
v1.21.2

KubeEdge v1.21.2 is a feature release combining v1.21.1 fixes with new capabilities: v1alpha2 node job APIs now default (v1alpha1 deprecated), ConfigUpdateJob CRD for cloud-driven config updates, and closed-loop flow control for node groups. Operators must prepare for four breaking changes: node jobs are disabled by default in EdgeCore, keadm upgrade no longer auto-backs up, v1alpha1 node job APIs are unmaintained, and keadm upgrade business flags are hidden.

  • breakingNodeUpgradeJob/ImagePrePullJob default to v1alpha2; v1alpha1 deprecated

    v1alpha2 is now the default for NodeUpgradeJob and ImagePrePullJob. The v1alpha1 versions remain supported with backward-compatible CRDs but will be unmaintained starting now and removed after v1.23. To continue using v1alpha1, set the feature gates in ControllerManager and CloudCore.

  • breakingNode job module disabled by default in EdgeCore

    The node job Beehive module in EdgeCore is now disabled by default. Existing deployments relying on NodeUpgradeJob or ImagePrePullJob must enable the module in edgecore.yaml or node jobs will not run.

  • breakingkeadm upgrade no longer backs up automatically

    The keadm upgrade command no longer automatically backs up the cluster state. Manual backup via the separate backup command is now required before upgrades.

  • breakingkeadm upgrade business-related flags deprecated

    Flags related to business logic in the keadm upgrade command are hidden and will be removed after v1.23. Any workflows depending on these flags must be refactored.

Key changes (8)
  • v1alpha2 NodeUpgradeJob/ImagePrePullJob now default, v1alpha1 deprecated; opt-out via ControllerManager/CloudCore feature gates; removal after v1.23
  • Node job Beehive module disabled by default in EdgeCore; requires edgecore.yaml to enable
  • keadm upgrade no longer auto-backs up; manual backup command needed before upgrades
  • Node Task API v1alpha2 redesigned with Phase field (Init/InProgress/Completed/Failure) and nodeStatus subfields for improved error tracking
  • ConfigUpdateJob CRD added for cloud-driven EdgeCore config updates; disabled by default, requires TaskManager enable and EdgeCore restart to apply
  • Closed-loop flow control added for node groups, restricting cross-group service access
  • Dashboard enhanced with BFF layer and keink one-click cluster launch
  • Fixed: NodeUpgradeJob runner registration, policyManager reconciliation, Lease parsing, keadm reset edge container removal, mapper-framework data push
Source ↗
Browse by month
Jul 2026Jun 2026May 2026Apr 2026Mar 2026Feb 2026Jan 2026Dec 2025Nov 2025Oct 2025Sep 2025Aug 2025Jul 2025Jun 2025May 2025Apr 2025