Etcd Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
=Overview= | =Overview= | ||
etcd is a distributed, highly available key/value datastore for state within a cluster. etcd is used by [[Kubernetes_Control_Plane_and_Data_Plane_Concepts#Cluster_Store|Kubernetes cluster store]] to maintain configuration and other state. etcd is designed for large scale distributed systems, that will never tolerate split brain operation (network partitions) 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 is a distributed, highly available key/value datastore for state within a cluster. etcd is used by [[Kubernetes_Control_Plane_and_Data_Plane_Concepts#Cluster_Store|Kubernetes cluster store]] to maintain configuration and other state. etcd is designed for large scale distributed systems, that will never tolerate split brain operation (network partitions) and are willing to sacrifice availability to achieve this. etcd prefers consistence over availability. 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. | ||
Revision as of 01:05, 21 August 2019
Internal
Overview
etcd is a distributed, highly available key/value datastore for state within a cluster. etcd is used by Kubernetes cluster store to maintain configuration and other state. etcd is designed for large scale distributed systems, that will never tolerate split brain operation (network partitions) and are willing to sacrifice availability to achieve this. etcd prefers consistence over availability. Also see the CAP Theorem. etcd can be used as a consistent key-value store for configuration management, service discovery and coordinating distributed work.