# KubeEdge v1.21.1

2025-12-17 · [Original release notes](https://github.com/kubeedge/kubeedge/releases/tag/v1.21.1) · [Full summary](https://ratatosk.io/en/releases/kubeedge/v1.21.1)

Breaking changes 3 · Important fixes 6 · Enhancements 1 · Other changes 3

## Breaking changes (3)

### MySQL `ReportCycle` now uses millisecond units

- Affects: mapper-framework setups using the MySQL database method and `ReportCycle` (Inferred)

Previously, the MySQL handler converted `ReportCycle` directly to `time.Duration` without applying a time unit.

Evidence: “+ reportCycle := time.Millisecond * time.Duration(twin.Property.ReportCycle)” https://github.com/kubeedge/kubeedge/pull/6578

> - Fix data push operation in mapper-framework. ([#6578](https://github.com/kubeedge/kubeedge/pull/6578), [@aAAaqwq](https://github.com/aAAaqwq))

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md

### Redis sorted-set members now store JSON-marshaled data

- Affects: Redis sorted-set members written by the mapper-framework Redis database method (Inferred)

Previously, members were formatted strings containing `TimeStamp`, `PropertyName`, and `data.Value`; they now contain the JSON-marshaled data object, while the sorted-set score remains based on `data.TimeStamp`.

Evidence: “- deviceData := "TimeStamp: " + strconv.FormatInt(data.TimeStamp, 10) + " PropertyName: " + data.PropertyName + " data: " + data.Value” https://github.com/kubeedge/kubeedge/pull/6578

> - Fix data push operation in mapper-framework. ([#6578](https://github.com/kubeedge/kubeedge/pull/6578), [@aAAaqwq](https://github.com/aAAaqwq))

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md

### Mapper-framework MQTT configuration now uses the `mqtt` JSON key

- Affects: mapper-framework setups configuring the MQTT publish method through JSON (Inferred)

Previously, the MQTT configuration field used the `http` JSON key.

Evidence: “- MQTT *MQTTConfig `json:"http"`” https://github.com/kubeedge/kubeedge/pull/6578

> - Fix data push operation in mapper-framework. ([#6578](https://github.com/kubeedge/kubeedge/pull/6578), [@aAAaqwq](https://github.com/aAAaqwq))

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md

## Important fixes (6)

### PolicyManager reconciliation uses non-cached reads

- Affects: cloud PolicyManager policy reconciliation (Inferred)

When recently created Pods were not visible to cached reads, PolicyManager could make wrong reconciliation decisions and skip `send2Edge()` for some nodes. Reconciliation lookups now use the non-cached reader.

> - Fix policyManager reconciliation with non-cached reader. ([#6558](https://github.com/kubeedge/kubeedge/pull/6558), [@mkhon](https://github.com/mkhon))

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md

### PolicyManager Pod update reconciliation fixed

- Affects: PolicyManager setups with matching Pods

DaemonSet Pods were initially created without `.Spec.NodeName` and filtered out, then their updates did not trigger reconciliation. Now an update to a matching Pod can trigger reconciliation after its initial creation was filtered out.

> - Fix policyManager reconciliation with non-cached reader. ([#6558](https://github.com/kubeedge/kubeedge/pull/6558), [@mkhon](https://github.com/mkhon))

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md

### MetaServer Leases kind conversion fixed

- Affects: setups where MetaServer handles Leases resources or kinds (Inferred)

When MetaServer parsed Leases, it produced `Leas` instead of `Leases`. The conversion now maps `leases` to `Leases` and `Leases` to `leases`.

> - Fix Leases being parsed as Leas in MetaServer. ([#6567](https://github.com/kubeedge/kubeedge/pull/6567), [@brinker-tbaker](https://github.com/brinker-tbaker))

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md

### `keadm reset` container removal fixed

- Affects: edge resets using `keadm reset` to remove KubeEdge-managed containers (Inferred)

On edge resets, containers were not removed when the reset flow missed connecting to the container runtime first. The utility now connects before listing Kube containers and returns an error if that connection fails.

> - Fix keadm reset edge failed to remove containers for containerRuntime.Connect missed. ([#6575](https://github.com/kubeedge/kubeedge/pull/6575), [@will4j](https://github.com/will4j))

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md

### Mapper-framework MQTT publisher no longer exits on broker connection errors

- Affects: mapper-framework setups using the MQTT publisher

Previously, a failed broker connection printed the error and terminated the process. Now the error is logged and `Push` returns without exiting the process.

> - Fix data push operation in mapper-framework. ([#6578](https://github.com/kubeedge/kubeedge/pull/6578), [@aAAaqwq](https://github.com/aAAaqwq))

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md

### Mapper-framework OpenTelemetry device-data type assertion replaced

- Affects: Mapper-framework setups using the OpenTelemetry data handler and supplying device data to it (Inferred)

Previously, the handler passed data to `ObserveFloat64` through a direct `float64` type assertion. It now converts data to a string, parses it as `float64`, and observes the parsed value; conversion or parsing failures return errors.

> - Fix data push operation in mapper-framework. ([#6578](https://github.com/kubeedge/kubeedge/pull/6578), [@aAAaqwq](https://github.com/aAAaqwq))

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md

## Enhancements (1)

- PolicyManager adds detailed `send2Edge` logging (To use: `klog.V(4)` log verbosity)

## Other changes (3)

- NodeUpgradeJob runner registration uses `ResourceNodeUpgradeJob`
- MySQL initialization error log message corrected
- Mapper device data handler removes direct database calls

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
