# Kubernetes v1.32

Kubernetes v1.32, code-named Penelope, is a release series of the Kubernetes container orchestration system.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## 【kube-apiserver】Watch cache / cacher：dispatch、bookmark 与穿透 etcd

DevFeed: [【kube-apiserver】Watch cache / cacher：dispatch、bookmark 与穿透 etcd](<https://devfeed.tech/articles/kube-apiserver-watch-cache-cacher-dispatch-bookmark-etcd-33961.md>)

Original publisher: [Read original article](<https://quant67.com/post/apiserver/05-watch-cache/05-watch-cache.html>)

Author: Liao Tonglang

Published: 2026-08-28T00:00:00Z

Content type: article

Language: zh

Sources: [土法炼钢 - 系统与基础设施](<https://devfeed.tech/sources/source-4.md>)

Topics: [Caching](<https://devfeed.tech/topics/caching.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [API](<https://devfeed.tech/topics/api.md>), [Kubernetes v1.32](<https://devfeed.tech/topics/kubernetes-v1-32.md>)

Tags: [410-gone](<https://devfeed.tech/tags/410-gone.md>), [apiserver](<https://devfeed.tech/tags/apiserver.md>), [bookmark](<https://devfeed.tech/tags/bookmark.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cacher](<https://devfeed.tech/tags/cacher.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [resourceversion](<https://devfeed.tech/tags/resourceversion.md>), [storage](<https://devfeed.tech/tags/storage.md>), [v1](<https://devfeed.tech/tags/v1.md>), [v1-30-3](<https://devfeed.tech/tags/v1-30-3.md>), [watch-cache](<https://devfeed.tech/tags/watch-cache.md>)

### AI overview

This article explains the Kubernetes v1.30.3 apiserver watch cache and cacher implementation. It covers the watchCache sliding window, the Ready gate during startup synchronization, in-memory event dispatch, bookmark progress notifications, and the conditions that cause cache misses to fall back to etcd.

### Source excerpt

钉 Kubernetes v1.30.3 cacher 对 storage.Interface 的包装：watchCache 滑动窗口与 Ready 门、bookmark 推送路径、cache miss 打穿 etcd 的触发条件，以及 List 风暴成因与 watch cache SLO 与 compaction 间隔之间的开放问题。

## Kubernetes v1.36: Server-Side Sharded List and Watch

DevFeed: [Kubernetes v1.36: Server-Side Sharded List and Watch](<https://devfeed.tech/articles/kubernetes-v1-36-server-side-sharded-list-and-watch-4547.md>)

Original publisher: [Read original article](<https://kubernetes.io/blog/2026/05/06/kubernetes-v1-36-server-side-sharded-list-and-watch/>)

Author: Jeffrey Ying

Published: 2026-05-06T18:35:00Z

Content type: article

Language: en

Sources: [Kubernetes Blog](<https://devfeed.tech/sources/kubernetes-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Kubernetes v1.32](<https://devfeed.tech/topics/kubernetes-v1-32.md>), [API](<https://devfeed.tech/topics/api.md>), [servers](<https://devfeed.tech/topics/servers.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [memory](<https://devfeed.tech/tags/memory.md>), [network](<https://devfeed.tech/tags/network.md>), [v1](<https://devfeed.tech/tags/v1.md>)

### AI overview

Kubernetes v1.36 introduces server-side sharded list and watch as an alpha feature. The API server filters high-cardinality resource events by deterministic hash ranges, reducing unnecessary CPU, memory, and network usage for horizontally scaled controllers.

### Source excerpt

As Kubernetes clusters grow to tens of thousands of nodes, controllers that watch high-cardinality resources like Pods face a scaling wall. Every replica of a horizontally scaled controller receives the full stream of events from the API server, paying the CPU, memory, and network cost to deserialize everything, only to discard the objects it is not responsible for. Scaling out the controller does not reduce per-replica cost; it multiplies it. Kubernetes v1.36 introduces server-side sharded list and watch as an alpha feature (KEP-5866). With this feature enabled, the API server filters events at the source so that each controller replica receives only the slice of the resource collection it owns. The problem with client-side sharding Some controllers, such as kube-state-metrics, already support horizontal sharding. Each replica is assigned a portion of the keyspace and discards objects that do not belong to it. While this works functionally, it does not reduce the volume of data flowing from the API server: N replicas x full event stream: every replica deserializes and processes every event, then throws away what it does not need. Network bandwidth scales with replicas, not with shard size. CPU spent on deserialization is wasted for the discarded fraction. Server-side sharded list and watch solves this by moving the filtering upstream into the API server. Each replica tells the API server which hash range it owns, and the API server only sends matching events. How it works The feature adds a shardSelector field to ListOptions. Clients specify a hash range using the shardRange() function: shardRange(object.metadata.uid, '0x0000000000000000', '0x8000000000000000') The API server computes a deterministic 64-bit FNV-1a hash of the specified field and returns only objects whose hash falls within the range [start, end). This applies to both list responses and watch event streams. The hash function produces the same result across all API server instances, so the feature is