---
title: "etcd"
description: "1 posts about etcd, summarised, each linking to the original."
---

# etcd
> 1 posts about etcd, summarised, each linking to the original.

## Articles

### [Sharding etcd on hosted control planes and what the numbers actually say](https://yomu.fyi/post/sharding-etcd-on-hosted-control-planes-and-what-the-numbers-actually-s.md)
- Company: [Red Hat](https://yomu.fyi/company/red-hat.md)
- Author: Vishnu Challa
- Published: Oct 13, 2026
- Type: Benchmark

Sharding etcd on hosted control planes splits the key-value store into multiple instances by resource kind, a tech preview feature tested with a main shard for cluster state and a dedicated events shard on Red Hat OpenShift 4.21 with HyperShift. Under event pressure from synthetic storms and realistic crashlooping pods, the sharded configuration showed up to 96% fewer slow applies, faster compaction and raft snapshot durations, and 60% more WAL fsyncs and 90% more backend commits combined. The sharded arm never failed the event storm workload, while the standard arm occasionally did. Pod-ready latencies and workload finish times remained comparable across both configurations. The trade-offs are roughly 1.8 to 2.3 times the etcd container memory and a compaction regression under large custom resource quota pressure that is still under investigation.