# Kubernetes v1.37: etcd RangeStream Cuts Memory Use on Large List Reads

Publisher-attributed story with a reviewed brief or permitted publisher paragraph. The original publisher is responsible for the linked reporting.

- Publisher: Kubernetes
- Category: Infrastructure
- Original publication time: 2026-09-01T18:30:00Z
- First observed by NexusTechWire: 2026-10-01T15:54:35Z
- Original source: https://kubernetes.io/blog/2026/09/01/kubernetes-v1-37-etcd-range-stream/
- NexusTechWire record: https://nexustechwire.com/news/news-4db85808102385e4d30e

## From the publisher

I am excited to announce that etcd RangeStream is graduating to beta in Kubernetes v1.37. Paired with etcd v3.7, it reduces the memory the API server and etcd need to read a large collection, and makes peak usage more predictable. The cost of large reads The API server serves most list and watch requests from its in-memory watch cache. Populating that cache requires reading a resource's full state from etcd, at startup and on every re-initialization. For a resource with many objects, or large ones, such as Pods, that read is expensive. The API server already paginated these reads, asking etcd for a fixed number of keys at a time rather than the whole collection at once. But a page bounded by key count has no awareness of object size, so a page of large objects can still be very large.

Source license: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Publisher excerpt shortened and converted to plain text. Original source license applies.

Read the full original: [Kubernetes](https://kubernetes.io/blog/2026/09/01/kubernetes-v1-37-etcd-range-stream/)

This record does not reproduce the complete article or represent independent confirmation of every source claim.