etcd mit Homebrew installieren

Projektlinks

• Homepage
• Repository

Befehle und Aliase

• etcd
• etcdctl
• etcdutl

Projektgeschichte

The etcd project was created at CoreOS in 2013. Its design centers on a reliable key-value store written in Go and backed by the Raft consensus algorithm, with a user-facing gRPC API and a simple command-line client, `etcdctl`.

The project's own README emphasizes simplicity, TLS support, performance, and reliability through Raft. That positioning made etcd less a general database and more the small, dependable coordination store that other distributed systems could build around.

Adoptionsgeschichte

Kubernetes made etcd famous: CNCF described it as the primary data store for all Kubernetes clusters, storing and replicating cluster state while Raft handles failures and partitions. CNCF also named Cloud Foundry, CoreDNS, M3, Rook, TiKV, and other systems among etcd users or dependents.

In December 2018, CNCF accepted etcd as an incubation-level hosted project. In November 2020, CNCF announced etcd's graduation after demonstrating growing adoption, open governance, feature maturity, security audits, and community sustainability.

Wie es verwendet wird

The everyday package workflow is split between the `etcd` server and the `etcdctl` client. A user starts a single-node or clustered server listening on the standard client and peer ports, then uses commands such as `etcdctl put` and `etcdctl get` for key-value operations or higher-level features such as watches, leases, locks, and member management.

Operationally, etcd is treated as infrastructure state: it needs backups, monitoring, TLS, careful upgrade and downgrade paths, and cluster maintenance. That is why the documentation has substantial operations guides rather than only API examples.

Warum Paket-Nerds sich dafür interessieren

etcd is a package-manager landmark because a tiny set of binaries can become the persistence layer for a whole orchestration platform. The package ships server, client, and utility commands, and its versioning affects Kubernetes control planes, cloud products, and distribution test matrices.

It also represents the Go single-binary cloud-native packaging style: official release binaries for Linux, macOS, Windows, and Docker, a Homebrew formula, distro packages for clients, and source-level module boundaries for libraries.

Zeitleiste

• 2013: etcd is created at CoreOS.
• 2018: CNCF accepts etcd as an incubating project.
• 2020: etcd graduates from CNCF incubation.
• 2022: etcd integrates continuous fuzzing through OSS-Fuzz work.

Related projects

• Kubernetes is the best-known etcd user. The project is also associated with CoreOS, CNCF, Raft, CoreDNS, Cloud Foundry, M3, Rook, TiKV, and related cloud-native coordination systems.

Quellen

• https://github.com/etcd-io/etcd
• https://etcd.io/docs
• https://etcd.io/blog/2022/etcd-integrates-continuous-fuzzing/
• https://www.cncf.io/blog/2018/12/11/cncf-to-host-etcd/
• https://www.cncf.io/announcements/2020/11/24/cloud-native-computing-foundation-announces-etcd-graduation/