etcd v3.7.0 introduces RangeStream, drops v2store remnants, and delivers major performance gains

by

Overview

The Kubernetes SIG etcd (vendor claim) released etcd v3.7.0 on July 8 2026. This minor release adds a new RangeStream RPC, removes the last vestiges of the legacy v2 store, and completes a protobuf library overhaul. It also updates core dependencies – bbolt to v1.5.1 and raft to v3.7.0 – and introduces several performance and security enhancements.

Key New Features

  • RangeStream: Streams large result sets in chunks, reducing latency and memory pressure on both server and client (vendor claim).
  • Keys‑only range optimization: Reads only the in‑memory index for --keys-only requests, avoiding unnecessary bbolt reads (vendor claim).
  • Faster, more reliable leases: Prioritized LeaseRevoke and a new FastLeaseKeepAlive improve lease handling under load (vendor claim).
  • Unix socket support: Enables local communication without a TCP port for single‑member clusters, useful for development and edge devices (vendor claim).
  • Protobuf overhaul: Replaces golang/protobuf and gogo/protobuf with google.golang.org/protobuf, reducing CPU usage and improving maintainability (vendor claim).

Performance Improvements

According to the announcement, Kubernetes control‑plane components should see a noticeable drop in CPU consumption compared with etcd v3.6. The keys‑only optimization and faster find() operations for concurrent watches also cut backend reads and memory usage.

Upgrade Considerations

v3.7 removes the remaining v2store dependencies, meaning clusters must upgrade from v3.6.11 or later. The release contains breaking changes, so a rolling upgrade—one member at a time—paired with the official upgrade guide is recommended (vendor claim). Deprecated experimental flags have been removed, and feature‑gate lifecycle now follows the Kubernetes model.

Impact on Kubernetes

The EtcdRangeStream feature gate will be enabled by default in the upcoming Kubernetes v1.37, allowing native consumption of the new RPC without additional configuration.

Where to Get It

Binary releases, source archives, and official multi‑arch container images are available on the etcd website. The release is distributed only as multi‑arch containers; architecture‑specific tags are no longer provided.

References