Etcd Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
etcd is a distributed, highly available key/value datastore for state within a cluster. etcd is used by [[Kubernetes Concepts#etcd|Kubernetes]] and [[OpenShift Concepts#etcd|OpenShift]] to maintain configuration and other state. | etcd is a distributed, highly available key/value datastore for state within a cluster. etcd is used by [[Kubernetes Concepts#etcd|Kubernetes]] and [[OpenShift Concepts#etcd|OpenShift]] to maintain configuration and other state. | ||
etcd is designed for large scale distributed systems, that will never tolerate split brain operation and are willing to sacrifice availability to achieve this. | etcd is designed for large scale distributed systems, that will never tolerate split brain operation and are willing to sacrifice availability to achieve this. Also see [[Distributed_Systems#CAP_Theorem|the CAP Theorem]]. | ||
etcd can be used as a consistent key-value store for configuration management, service discovery and coordinating distributed work. | etcd can be used as a consistent key-value store for configuration management, service discovery and coordinating distributed work. | ||
Revision as of 22:15, 3 June 2019
Internal
Overview
etcd is a distributed, highly available key/value datastore for state within a cluster. etcd is used by Kubernetes and OpenShift to maintain configuration and other state.
etcd is designed for large scale distributed systems, that will never tolerate split brain operation and are willing to sacrifice availability to achieve this. Also see the CAP Theorem.
etcd can be used as a consistent key-value store for configuration management, service discovery and coordinating distributed work.