This GitHub fork packages the preserved etcd 2.3.7 storage and protocol boundary for PastureStack. The current package candidate is plain semantic version 2.3.8; if publication is separately approved, its image tag will be ghcr.io/pasturestack/etcd-compat:v2.3.8. The underlying upstream engine remains 2.3.7 and is explicitly identified as an end-of-life import boundary, not a supported etcd release.
The candidate uses a digest-pinned Ubuntu 26.04 base, the 20260808T000000Z Ubuntu package snapshot, exact direct-package versions, Go 1.26.5 with an archive checksum, and an exact checksum-verified helper source archive. A small maintained patch corrects the helper's formatting and integer-conversion defects so current compiler, vet, and race checks can run without suppressions. The release gate builds the current commit instead of reusing a previously published image.
The maintained health checks use mutual TLS and verify the managed service identity etcd.<stack>. Connecting through a container name or the loopback listener never disables certificate verification.
The preserved v3 client accepts Unix socket endpoints whose filenames contain a colon on current Go toolchains. Internal gRPC errors also use fixed format strings so Go 1.26 validation does not reinterpret upstream error text as a format string.
Three public private-key fixtures inherited from upstream remain only for the original HTTP/2 demo and etcd integration tests. They are unsafe for any deployment, are excluded from the runtime image, and are covered by exact path and content-hash gates. trivy-secret.yaml suppresses only those hash-pinned fixtures; every other detected secret blocks publication.
PastureStack is an independent community effort to preserve, audit, and modernize the Rancher 1.6 ecosystem. It is not affiliated with or endorsed by Rancher Labs or SUSE.
Upstream: rancher/etcd, in the public etcd fork network. This fork preserves upstream Git history, authorship, dates, tags, and license notices. PastureStack maintenance is consolidated into one commit after upstream version v2.3.7.
Existing compatibility artifacts remain immutable. Future PastureStack release versions use plain numeric semantic versions with no brand or maintenance-count suffix. The review-only etcd v2 data migration gate defines the sequential path and the blockers that must be closed before the compatibility runtime can be replaced.
See PASTURESTACK_MAINTENANCE.md, ORIGIN.md, COMPATIBILITY.md, SECURITY.md, and migration/README.md.
Note: The master branch may be in an unstable or even broken state during development. Please use releases instead of the master branch in order to get stable binaries.
etcd is a distributed, consistent key-value store for shared configuration and service discovery, with a focus on being:
- Simple: curl'able user-facing API (HTTP+JSON)
- Secure: optional SSL client cert authentication
- Fast: benchmarked 1000s of writes/s per instance
- Reliable: properly distributed using Raft
etcd is written in Go and uses the Raft consensus algorithm to manage a highly-available replicated log.
etcd is used in production by many companies, and the development team stands behind it in critical deployment scenarios, where etcd is frequently teamed with applications such as Kubernetes, fleet, locksmith, vulcand, and many others.
See etcdctl for a simple command line client.
Or feel free to just use curl, as in the examples below.
The easiest way to get etcd is to use one of the pre-built release binaries which are available for OSX, Linux, Windows, AppC (ACI), and Docker. Instructions for using these binaries are on the GitHub releases page.
For those wanting to try the very latest version, you can build the latest version of etcd from the master branch.
You will first need Go installed on your machine (version 1.4+ is required).
All development occurs on master, including new features and bug fixes.
Bug fixes are first targeted at master and subsequently ported to release branches, as described in the branch management guide.
First start a single-member cluster of etcd:
./bin/etcdThis will bring up etcd listening on port 2379 for client communication and on port 2380 for server-to-server communication.
Next, let's set a single key, and then retrieve it:
curl -L http://127.0.0.1:2379/v2/keys/mykey -XPUT -d value="this is awesome"
curl -L http://127.0.0.1:2379/v2/keys/mykey
You have successfully started an etcd and written a key to the store.
The official etcd ports are 2379 for client requests, and 2380 for peer communication. To maintain compatibility, some etcd configuration and documentation continues to refer to the legacy ports 4001 and 7001, but all new etcd use and discussion should adopt the IANA-assigned ports. The legacy ports 4001 and 7001 will be fully deprecated, and support for their use removed, in future etcd releases.
First install goreman, which manages Procfile-based applications.
Our Procfile script will set up a local example cluster. You can start it with:
goreman startThis will bring up 3 etcd members infra1, infra2 and infra3 and etcd proxy proxy, which runs locally and composes a cluster.
You can write a key to the cluster and retrieve the value back from any member or proxy.
Now it's time to dig into the full etcd API and other guides.
- Explore the full API.
- Set up a multi-machine cluster.
- Learn the config format, env variables and flags.
- Find language bindings and tools.
- Use TLS to secure an etcd cluster.
- Tune etcd.
- Upgrade from 0.4.9+ to 2.2.0.
- Mailing list: etcd-dev
- IRC: #etcd on freenode.org
- Planning/Roadmap: milestones, roadmap
- Bugs: issues
See CONTRIBUTING for details on submitting patches and the contribution workflow.
See reporting bugs for details about reporting any issue you may encounter.
GH518 is a known bug. Issue is that:
curl http://127.0.0.1:2379/v2/keys/foo -XPUT -d value=bar
curl http://127.0.0.1:2379/v2/keys/foo -XPUT -d dir=true -d prevExist=true
If the previous node is a key and client tries to overwrite it with dir=true, it does not give warnings such as Not a directory. Instead, the key is set to empty value.
etcd uses semantic versioning New minor versions may add additional features to the API.
You can get the version of etcd by issuing a request to /version:
curl -L http://127.0.0.1:2379/versionThe v2 API responses should not change after the 2.0.0 release but new features will be added over time.
etcd has known issues on 32-bit systems due to a bug in the Go runtime. See #358 for more information.
To avoid inadvertantly running a possibly unstable etcd server, etcd on 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 only the amd64 architecture is officially supported by etcd.
etcd is under the Apache 2.0 license. See the LICENSE file for details.