Skip to content

Module: ETCD

Pigsty deploys etcd as DCS for reliable distributed config storage, supporting PostgreSQL HA.

ETCD is a distributed, reliable key-value store for critical system configuration data.

Pigsty uses etcd as a DCS (Distributed Config Store). It is critical for PostgreSQL high availability and automatic failover.

The ETCD module depends on NODE. The PGSQL module requires ETCD. Install NODE to manage nodes before you install ETCD.

Deploy the ETCD cluster before any PGSQL cluster. For PostgreSQL high availability, patroni and vip-manager depend on etcd. They use it for HA and to bind the L2 VIP to the primary.

One etcd cluster serves multiple PostgreSQL clusters in each Pigsty deployment.

Pigsty enables RBAC by default. Each PostgreSQL cluster uses separate credentials to isolate tenants. Administrators use the etcd root user, which has full permissions over all PostgreSQL clusters.

Choose etcd cluster size based on requirements, provide reliable access.

ETCD module provides 13 configuration parameters for fine-grained control over cluster behavior.

etcd cluster management SOP: create, destroy, scale, config, and RBAC.

Manage etcd clusters with Ansible playbooks and quick command reference.

etcd monitoring dashboards, metrics, and alert rules.

Complete monitoring metrics list provided by Pigsty ETCD module

Frequently asked questions about Pigsty etcd module

Was this page helpful?