liveBook · Manning

Etcd

As explained in Google Anthos in Action

etcd is a distributed, strongly consistent key-value store used to persist Kubernetes cluster state and resource data.

etcd is the key-value database that maintains every Kubernetes resource and the entire cluster state. Without a functioning etcd database, the cluster cannot function. section 3.2.2

Operate etcd with these safeguards:

  • Run at least three replicas, and use an odd number so the cluster can elect a majority leader and reduce split-brain risk. section 3.2.2
  • Create regular backups outside the cluster so a lost or corrupted database can restore a node or the entire cluster. section 3.2.2
  • Protect the database because it contains every Kubernetes resource, including sensitive secrets that may be stored as clear text by default. section 3.2.2

How Google Anthos in Action covers it

How deep it goes
Explains storage responsibility, replica-count rationale, split-brain failure, backups, recovery, and clear-text security exposure.
Examples
Uses odd-numbered etcd replicas, external database backups, corrupted-cluster recovery, and stored Kubernetes secrets as operational examples.
What it assumes
Assumes familiarity with Kubernetes clusters, control-plane components, resources, replicas, and secrets.
What you can do after
Operate/configure etcd for quorum-based availability, external backups, cluster restoration, and protection of sensitive resource data.
How it connects
Connects Kubernetes control planes with cluster state, high availability, backups, split-brain recovery, and secrets security.

Also explained in

Compare how 2 books explain etcd →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.