# Knative knative-v1.20.1

2025-12-25 · [Original release notes](https://github.com/knative/serving/releases/tag/knative-v1.20.1) · [Full summary](https://ratatosk.io/en/releases/knative/knative-v1.20.1)

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

## Security (1)

### `AllowRootBounded` security-context defaults

- Affects: Revision workloads using the `secure-pod-defaults` feature setting (Inferred)
- Additional action: `secure-pod-defaults` set to `AllowRootBounded`

`AllowRootBounded` defaults `SeccompProfile` and `Capabilities` when they are nil, without applying the `runAsNonRoot` default used by `Enabled`. In v1.20, `secure-pod-defaults` remains disabled by default, so upgrading alone does not change Revision defaults.

> We've introduce `secure-pod-defaults` in an earlier release but this release includes a new setting `AllowRootBounded` that offers a better security posture for your workloads but balances the compatibility with images that require/expect you to run as root.

## Breaking changes (2)

### Serving metric names updated

- Affects: Serving metric queries or dashboards using `kn.queueproxy.app.duration` or `kn.queueproxy.depth` (Inferred)

Serving now emits `kn.serving.invocation.duration` and `kn.serving.queue.depth` instead of `kn.queueproxy.app.duration` and `kn.queueproxy.depth`.

Evidence: “Fix metric names to match the original design document `kn.queueproxy.app.duration` becomes `kn.serving.invocation.duration` and `kn.queueproxy.depth` becomes `kn.serving.queue.depth`” https://github.com/knative/serving/pull/16293

> * [release-1.20] Fix Serving Metric Names to match Design Document by @knative-prow-robot in https://github.com/knative/serving/pull/16293

### Autoscaler service stats metrics drop `RevisionNameKey`

- Affects: Setups consuming autoscaler service stats metrics that use `RevisionNameKey` (Inferred)

Before this release, the scraper attached the revision name to these metrics as `RevisionNameKey`.

> * [release-1.20] Make autoscaler instrument async so we can remove metric attributes when revisions go away by @knative-prow-robot in https://github.com/knative/serving/pull/16302

## Important fixes (3)

### Knative Serving preserves external metadata during reconciliation

- Affects: Serving Deployments or pod templates with external labels or annotations (Inferred)

Knative-controlled `knative.dev` keys and the app label use desired values; other metadata keys are preserved from the current resources.

> * [release-1.20] Preserve deployment and its template labels and annotations by @knative-prow-robot in https://github.com/knative/serving/pull/16303

### Unbounded autoscaler metric growth fixed

- Affects: Knative Serving autoscaler metrics collection (Inferred)

When revision metric attributes could not be removed after revisions went away, metric data could grow without bound. Autoscaler metrics now use observable gauges, and their registrations can be unregistered when the related scaler resources are deleted.

> * [release-1.20] Make autoscaler instrument async so we can remove metric attributes when revisions go away by @knative-prow-robot in https://github.com/knative/serving/pull/16302

### Serving now suppresses the “default value insecure” warning

- Affects: Serving setups with `SecurePodDefaults` set to `Enabled` or `AllowRootBounded`

This includes the tested incomplete security-context case.

> * [release-1.20] Suppress 'default value insecure' warning when secure-pod-defaults is enabled. by @knative-prow-robot in https://github.com/knative/serving/pull/16220

## Dependency updates (1)

1 more, none mentioning security

- `* [release-1.20] Upgrade to latest dependencies by @knative-automation in https://github.com/knative/serving/pull/16319`

---

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