# KEDA v2.21.1

2026-11-15 · [Original release notes](https://github.com/kedacore/keda/releases/tag/v2.21.1) · [Full summary](https://ratatosk.io/en/releases/keda/v2.21.1)

Security 1 · Breaking changes 3 · Important fixes 2 · Dependency updates 3 · Other changes 1

## Security (1)

### Unowned `HPA` protection in `ScaledObject` controllers

- Affects: ScaledObjects configured with the name of an unowned `HPA`

When a configured name matches an `HPA` owned by another resource, the controller leaves it untouched and reports an error. It can take over an unowned `HPA` only when ownership transfer is requested and it scales the same workload, or when the `HPA` opts out of ownership validation.

> - [`43b5dfc`](https://github.com/kedacore/keda/commit/43b5dfcd7a0a8a08e328b65667464986f60ee12c) : **General**: Only manage HPAs owned by the ScaledObject ([#8374](https://github.com/kedacore/keda/pull/8374)) (@keda-cherry-pick-bot[bot])

## Breaking changes (3)

### ArangoDB scaler now caps connections per endpoint

- Affects: ArangoDB scaler configurations with `connectionLimit` configured

A positive `connectionLimit` caps concurrent connections to each endpoint; unset or zero remains unlimited, and negative values fail validation.

> - [`cd6f868`](https://github.com/kedacore/keda/commit/cd6f868230952792a5a4eb6f1800039b22a48f93) : **ArangoDB Scaler**: Limit connections to connectionLimit ([#8343](https://github.com/kedacore/keda/pull/8343)) (@keda-cherry-pick-bot[bot])

### Splunk Observability scaler uses configured metric types

- Affects: Splunk Observability scaler triggers using `Value` or `AverageValue`

Previously, the scaler generated a `Value` target even when a trigger specified `AverageValue`. It now uses the configured `Value` or `AverageValue` target, defaults to `Value` when `metricType` is omitted, and rejects `Utilization`.

> - [`b338b60`](https://github.com/kedacore/keda/commit/b338b6056d291b95441976f56267e780513dfa04) : **Splunk Observability Scaler**: Honour trigger metricType ([#8366](https://github.com/kedacore/keda/pull/8366)) (@keda-cherry-pick-bot[bot])

### InfluxDB scaler query-result error handling corrected

- Affects: setups using the InfluxDB scaler (Inferred)

When an InfluxDB v2 result could not be parsed, its error could be treated as no results; when an InfluxDB v3 stream failed mid-read, it could be reported as success with only a partial value. The scaler now returns these query-result errors.

> - [`dd8d47d`](https://github.com/kedacore/keda/commit/dd8d47de655a105bbe8375d41c470f5386e89ba7) : **InfluxDB Scaler**: Surface query result errors instead of masking them as an empty result ([#8305](https://github.com/kedacore/keda/pull/8305)) (@keda-cherry-pick-bot[bot])

## Important fixes (2)

### gRPC received-message counter no longer counts stream EOF

- Affects: setups that expose or consume the `keda_grpc_client_msg_received_total` metric for gRPC client streams (Inferred)

For gRPC client streams ending in `io.EOF`, the previous middleware counted the final EOF as a received message, adding one to the counter per stream. The counter now increments only for successfully received messages, so it is one lower for each such stream.

> - [`47f6e4b`](https://github.com/kedacore/keda/commit/47f6e4bc573fb63796c1b1ab4e953b6fa5d12186) : **Dependencies**: Update all dependencies retaining Kubernetes 1.36 (#8361) ([#8365](https://github.com/kedacore/keda/pull/8365)) (@JorTurFer)

### MySQL scaler connection-pool leak on failed initial ping fixed

- Affects: setups using the MySQL scaler

Before this fix, a failed initial ping left the pool and its connection-opener goroutine open, potentially leaking them across repeated failed scaler builds. The pool now closes when that ping fails, while the scaler still returns the ping error.

> - [`177da25`](https://github.com/kedacore/keda/commit/177da2554c74cb0400defc3cc760a1e387cd557d) : **MySQL Scaler**: close sql.DB when the initial ping fails ([#8369](https://github.com/kedacore/keda/pull/8369)) (@keda-cherry-pick-bot[bot])

## Dependency updates (3)

3 more, none mentioning security

- `` - [`3b98b80`](https://github.com/kedacore/keda/commit/3b98b806ff8754873ca9f655a75c2c61eb31cfc5) : **Dependencies**: Update Go toolchain to v1.27.3 (release/v2.21) ([#8316](https://github.com/kedacore/keda/pull/8316)) (@JorTurFer) ``
- `` - [`47f6e4b`](https://github.com/kedacore/keda/commit/47f6e4bc573fb63796c1b1ab4e953b6fa5d12186) : **Dependencies**: Update all dependencies retaining Kubernetes 1.36 (#8361) ([#8365](https://github.com/kedacore/keda/pull/8365)) (@JorTurFer) ``
- `` - [`7ea8aa0`](https://github.com/kedacore/keda/commit/7ea8aa0e73088d1d0b1466654b813158f7e79dc4) : **Dependencies**: Update gcr.io/distroless/static:nonroot Docker digest to 18f4cc2 ([#8315](https://github.com/kedacore/keda/pull/8315)) (@keda-cherry-pick-bot[bot]) ``

## Other changes (1)

- KEDA skips cache updates and reconciliation for unchanged streamed metric specs

---

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