Version 3.3.12 home Download and build Libraries and tools Branch management Demo Discovery service protocol etcd release guide Frequently Asked Questions (FAQ) Logging conventions Metrics Production users Reporting bugs Tuning Benchmarks Benchmarking etcd v2.1.0 Benchmarking etcd v2.2.0 Benchmarking etcd v2.2.0-rc Benchmarking etcd v2.2.0-rc-memory Benchmarking etcd v3 Storage Memory Usage Benchmark Watch Memory Usage Benchmark Developer guide etcd API Reference etcd concurrency API Reference Experimental APIs and features gRPC naming and discovery Interacting with etcd Set up a local cluster System limits Why gRPC gateway etcd v3 API Learning etcd client architecture Client feature matrix Data model etcd v3 authentication design etcd versus other key-value stores etcd3 API Glossary KV API guarantees Learner Operations guide Clustering Guide Configuration flags Design of runtime reconfiguration Disaster recovery etcd gateway Failure modes gRPC proxy Hardware recommendations Maintenance Migrate applications from using API v2 to API v3 Monitoring etcd Performance Role-based access control Run etcd clusters inside containers Runtime reconfiguration Supported systems Transport security model Versioning Platforms Amazon Web Services Container Linux with systemd FreeBSD Upgrading Upgrade etcd from 2.3 to 3.0 Upgrade etcd from 3.0 to 3.1 Upgrade etcd from 3.1 to 3.2 Upgrade etcd from 3.2 to 3.3 Upgrade etcd from 3.3 to 3.4 Upgrade etcd from 3.4 to 3.5 Upgrading etcd clusters and applications

Supported systems

You are viewing documentation for etcd version: v3.3.12

etcd v3.3.12 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest release, v3.4.0, or the current documentation.

Current support

The following table lists etcd support status for common architectures and operating systems:

ArchitectureOperating SystemStatusMaintainers
amd64DarwinExperimentaletcd maintainers
amd64LinuxStableetcd maintainers
ppc64leLinuxStableetcd maintainers, @mkumatag

Experimental platforms appear to work in practice and have some platform specific code in etcd, but do not fully conform to the stable support policy. Unstable platforms have been lightly tested, but less than experimental. Unlisted architecture and operating system pairs are currently unsupported; caveat emptor.

Supporting a new system platform

For etcd to officially support a new platform as stable, a few requirements are necessary to ensure acceptable quality:

  1. An “official” maintainer for the platform with clear motivation; someone must be responsible for taking care of the platform.
  2. Set up CI for build; etcd must compile.
  3. Set up CI for running unit tests; etcd must pass simple tests.
  4. Set up CI (TravisCI, SemaphoreCI or Jenkins) for running integration tests; etcd must pass intensive tests.
  5. (Optional) Set up a functional testing cluster; an etcd cluster should survive stress testing.

32-bit and other unsupported systems

etcd has known issues on 32-bit systems due to a bug in the Go runtime. See the Go issue and atomic package for more information.

To avoid inadvertently running a possibly unstable etcd server, etcd on unstable or unsupported architectures will print a warning message and immediately exit if the environment variable ETCD_UNSUPPORTED_ARCH is not set to the target architecture.

Currently amd64 and ppc64le architectures are officially supported by etcd.

Supported systems