Discofork
Repository brief

etcd-io/etcd

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T11:46:33.850Z
3mo ago

etcd-io/etcd

etcd-io/etcd is a large, active Go repository for etcd, a distributed reliable key-value store for critical distributed-system data. It is heavily forked and starred, with recent commits on March 29-30, 2026 showing ongoing development. Forks are likely interesting if you care about a mature, production-grade distributed storage/control-plane component with active maintenance and a broad ecosystem.

GitHub
Loading tags...
Stars51,677
Forks10,338
Default branchmain
Last pushed2026-03-30T07:33:17Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if you need its legacy Alibaba-specific behavior and are prepared to maintain it yourself. For most adopters, current upstream etcd is the safer choice because this fork is stale and substantially behind.

Prefer this fork only if you want a heavily annotated, study-oriented etcd codebase. If you need a maintained, production-ready etcd, upstream is the better choice.

Prefer this fork only if you need a frozen, heavily customized legacy etcd branch and are prepared to own the maintenance. For most adopters, upstream is the better choice because this fork is materially stale and far behind on fixes and reliability work.

Prefer upstream unless you are maintaining a legacy deployment that depends on this fork’s dashboard/discovery customizations. The fork looks materially stale and far behind modern etcd, so its value is mainly compatibility with old behavior, not a better current platform.

Prefer this fork only if you specifically want its robustness-testing and traffic-modeling work. For production etcd usage, upstream is the better default because this fork is stale and materially behind.

Choose this fork if you need OpenShift-aligned operational workflows and downstream packaging/build integration. Choose upstream etcd if you want faster access to current fixes, less divergence, and a more general-purpose distribution.

Prefer this fork only if you need its specific historical customizations and are willing to own a large, stale divergence. For almost everyone else, upstream etcd is the better choice because it is far more current, maintained, and operationally safer.

Choose this fork only if you specifically need its older local patches or legacy behavior. For most adopters, upstream etcd is the better choice because this fork is materially stale and heavily diverged.

Prefer this fork only if you specifically need the k3s-maintained snapshot and are comfortable absorbing upstream lag. Otherwise, upstream etcd is the better choice because this fork shows no added features and is substantially behind on fixes.

Prefer this fork only if you explicitly need its older customized behavior. For most adopters, upstream etcd is the better choice because this fork is materially stale and far behind current fixes and maintenance.

etcd-io/etcd · Discofork