Previous change logs can be found at CHANGELOG-3.4.
See code changes and v3.5 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.5 upgrade guide.
/v3 endpoint.
/v3beta.curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}' does work in v3.5. Use curl -L http://localhost:2379/v3/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}' instead.etcd --log-output flag has been deprecated. Use etcd --log-outputs instead.etcd --logger=zap --log-outputs=stderr is now the default.etcd --logger=capnslog flag has been deprecated.etcd --logger=zap --log-outputs=default flag value is not supported..
etcd --logger=zap --log-outputs=stderr.etcd --logger=zap --log-outputs=systemd/journal to send logs to the local systemd journal.etcd --logger=capnslog --log-outputs=default redirects server logs to local systemd journal. And if write to journald fails, it writes to os.Stderr as a fallback.os.Stderr, which is inefficient.etcd --log-outputs=stderr is now the default.etcd --log-package-levels flag for capnslog has been deprecated. Now, etcd --logger=zap --log-outputs=stderr is the default.[CLIENT-URL]/config/local/log endpoint has been deprecated, as is etcd --log-package-levels flag.
curl http://127.0.0.1:2379/config/local/log -XPUT -d '{"Level":"DEBUG"}' won't work.etcd --logger=zap --log-outputs=stderr instead.etcd_debugging_mvcc_db_total_size_in_bytes Prometheus metric. Instead, use etcd_mvcc_db_total_size_in_bytes.Note that any etcd_debugging_* metrics are experimental and subject to change.
etcd_debugging_mvcc_db_total_size_in_bytes Prometheus metric. Instead, use etcd_mvcc_db_total_size_in_bytes./v3 endpoint.
/v3beta.curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}' does work in v3.5. Use curl -L http://localhost:2379/v3/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}' instead.