etcd is a production-ready store for building cloud-native distributed systems and managing cloud-native infrastructure via orchestrators like Kubernetes. Etcd should provide distributed system primitives** (such as distributed locking and leader election) that allow users to **create scalable, highly available and fault-tolerant systems. Etcd is the place to store the infrastructure configuration, not only as part of Kubernetes, but also as a standalone solution.
The charter defines the scope and governance of the etcd Special Interest Group.
Joining the mailing list for the group will typically add invites for the following meetings to your calendar.
- Regular SIG Meeting: Thursdays at 11:00 PT (Pacific Time) (biweekly). Convert to your timezone.
- Robustness Tests Meeting: Wednesdays at 11:00 PT (Pacific Time) (biweekly). Convert to your timezone.
- Triage Meeting: Thursdays at 11:00 PT (Pacific Time) (biweekly). Convert to your timezone.
The Chairs of the SIG run operations and processes governing the SIG.
- James Blair (@jmhbnz), Red Hat
- Wenjia Zhang (@wenjiaswe), Google
The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.
- Benjamin Wang (@ahrtr), VMware
- Marek Siarkowicz (@serathius), Google
- Slack: #sig-etcd
- Mailing list
- Open Community Issues/PRs
- GitHub Teams:
- @kubernetes/sig-etcd-leads - SIG Chairs and Tech Leads
- Steering Committee Liaison: Antonio Ojea (@aojea)
The following working groups are sponsored by sig-etcd:
The following subprojects are owned by sig-etcd:
Directly access data objects stored in etcd by kubernetes.
- Owners:
An embedded key/value database for Go.
- Owners:
Serve Consul with etcd
- Owners:
Distributed database benchmark tester
- Owners:
Kubernetes manifests powering discovery.etcd.io
- Owners:
Public etcd Discovery Service
- Owners:
Distributed reliable key-value store for the most critical data of a distributed system
- Owners:
etcd manager
- Owners:
etcd playground
- Owners:
etcd playground
- Owners:
failpoints for go
- Owners:
Use a custom domain in your Go import path
- Owners:
etcd java client
- Owners:
issue tracking for project wide non-code concerns
- Owners:
protodoc generates Protocol Buffer documentation.
- Owners:
Raft library for maintaining a replicated state machine
- Owners:
etcd-io
- Owners:
Serve the Apache Zookeeper API but back it with an etcd cluster
- Owners: