etcd stores small pieces of shared state as keys and values, with several members agreeing on changes so clients have a consistent view. Applications can watch values for updates, making it useful for configuration and coordination. Kubernetes itself uses etcd for cluster state, but an application-owned etcd deployment has a different owner and recovery process. Identify which role an installation serves before changing its members or restoring its data.
Deployment and operating notes
etcd remains a quorum-based key-value store with versioned operational and disaster-recovery documentation. The old Helm entry is not an instruction to replace the etcd cluster backing Kubernetes itself. On a managed Kubernetes service, control-plane etcd is normally operated through the provider; on a self-managed control plane, use that distribution’s documented recovery path.
For an application-owned etcd cluster, inventory member identities, peer and client certificates, data directories, clients and supported upgrade sequence. Take and validate a snapshot before changing membership or versions. Quorum depends on voting members, so adding replicas casually or restarting a majority can cause an outage. Rehearse restore into a separate cluster and validate client reads, watches and lease behavior. Upstream recovery guidance includes revision handling relevant to watch-based consumers, especially Kubernetes. A PVC snapshot alone is not a complete documented recovery procedure. Keep credentials and the exact restore configuration protected and available outside the failed cluster; a chart rollback cannot repair lost quorum or corrupted data.
Historical upstream link check · 2026-10-09
The recorded upstream address redirects to https://etcd.io/ and returned HTTP 200 on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines. It’s open-source and available on GitHub. etcd gracefully handles leader elections during network partitions and will tolerate machine failure, including the leader.
Your applications can read and write data into etcd. A simple use-case is to store database connection details or feature flags in etcd as key value pairs. These values can be watched, allowing your app to reconfigure itself when they change.
Advanced uses take advantage of the consistency guarantees to implement database leader elections or do distributed locking across a cluster of workers.
This chart bootstraps an etcd deployment on a Kubernetes cluster using the Helm package manager.
Prerequisites
- Kubernetes 1.4+ with Beta APIs enabled
- PV provisioner support in the underlying infrastructure
New etcd users and developers should get started by downloading and building etcd. After getting etcd, follow the quick demo to see the basics of creating and working with an etcd cluster.
Sources & further reading
Spotted something that needs another look?
Help improve this page →