The following table lists etcd support status for common architectures and operating systems:
Architecture | Operating System | Status | Maintainers |
---|---|---|---|
amd64 | Darwin | Experimental | etcd maintainers |
amd64 | Linux | Stable | etcd maintainers |
amd64 | Windows | Experimental | |
arm64 | Linux | Experimental | @glevand |
arm | Linux | Unstable | |
386 | Linux | Unstable | |
ppc64le | Linux | Stable | etcd 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.
For etcd to officially support a new platform as stable, a few requirements are necessary to ensure acceptable quality:
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
.