1
1
---
2
2
layout : blog
3
- title : " Announcing Etcd v3.6.0"
4
- date : 2025-05-19T10 :00:00-08:00
3
+ title : " Announcing etcd v3.6.0"
4
+ date : 2025-05-15T16 :00:00-08:00
5
5
slug : announcing-etcd-3.6
6
6
author : >
7
7
Benjamin Wang (VMware by Broadcom)
8
+ canonicalUrl : " https://etcd.io/blog/2025/announcing-etcd-3.6/"
8
9
---
9
10
10
- ## Table of Contents
11
-
12
- - ** [ Introduction] ( #introduction ) **
13
- - ** [ Security] ( #security ) **
14
- - ** [ Features] ( #features ) **
15
- - [ Migration to v3store] ( #migration-to-v3store )
16
- - [ Downgrade] ( #downgrade )
17
- - [ Feature Gates] ( #feature-gates )
18
- - [ Livez/readyz checks] ( #livezreadyz-checks )
19
- - [ v3discovery] ( #v3discovery )
20
- - ** [ Performance] ( #performance ) **
21
- - [ Memory] ( #memory )
22
- - [ Throughput] ( #throughput )
23
- - ** [ Breaking changes] ( #breaking-changes ) **
24
- - [ Old Binaries Are Incompatible with New Schema Versions] ( #old-binaries-are-incompatible-with-new-schema-versions )
25
- - [ Peer Endpoints No Longer Serve Client Requests] ( #peer-endpoints-no-longer-serve-client-requests )
26
- - [ Clear boundary between etcdctl and etcdutl] ( #clear-boundary-between-etcdctl-and-etcdutl )
27
- - ** [ Critical bug fixes] ( #critical-bug-fixes ) **
28
- - ** [ Upgrade issue] ( #upgrade-issue ) **
29
- - ** [ Testing] ( #testing ) **
30
- - ** [ Platforms] ( #platforms ) **
31
- - ** [ Dependencies] ( #dependencies ) **
32
- - [ Dependency Bumping Guide] ( #dependency-bumping-guide )
33
- - [ Core Dependency Updates] ( #core-dependency-updates )
34
- - [ grpc-gateway@v2] ( #grpc-gatewayv2 )
35
- - [ grpc-ecosystem/go-grpc-middleware/providers/prometheus] ( #grpc-ecosystemgo-grpc-middlewareprovidersprometheus )
36
- - ** [ Community] ( #community ) **
37
- - [ etcd Becomes a Kubernetes SIG] ( #etcd-becomes-a-kubernetes-sig )
38
- - [ New Contributors, Maintainers, and Reviewers] ( #new-contributors-maintainers-and-reviewers )
39
- - [ New Release Team] ( #new-release-team )
40
- - [ Introducing the etcd Operator Working Group] ( #introducing-the-etcd-operator-working-group )
41
- - ** [ Future Development] ( #future-development ) **
42
-
43
- ## Introduction
11
+ _ This announcement originally [ appeared] ( https://etcd.io/blog/2025/announcing-etcd-3.6/ ) on the etcd blog._
44
12
45
13
Today, we are releasing [ etcd v3.6.0] [ ] , the first minor release since etcd v3.5.0 on June 15, 2021. This release
46
14
introduces several new features, makes significant progress on long-standing efforts like downgrade support and
@@ -107,7 +75,7 @@ etcd will then migrate the data schema in the background. Once complete, proceed
107
75
108
76
For details, refer to the [ Downgrade-3.6] guide.
109
77
110
- ### Feature Gates
78
+ ### Feature gates
111
79
112
80
In etcd v3.6.0, we introduced Kubernetes-style feature gates for managing new features. Previously, we
113
81
indicated unstable features through the ` --experimental ` prefix in feature flag names. The prefix was removed
@@ -116,7 +84,7 @@ to Beta, then GA, or get deprecated. This ensures a much smoother upgrade and do
116
84
117
85
See [ feature-gates] [ ] for details.
118
86
119
- ### Livez/ readyz checks
87
+ ### livez / readyz checks {#livezreadyz-checks}
120
88
121
89
etcd now supports ` /livez ` and ` /readyz ` endpoints, aligning with Kubernetes' Liveness and Readiness probes.
122
90
` /livez ` indicates whether the etcd instance is alive, while ` /readyz ` indicates when it is ready to serve requests.
@@ -187,15 +155,15 @@ write throughput of v3.6.0-rc.2 over v3.5.20, ranging from 3.86% to 28.37%._
187
155
This section highlights a few notable breaking changes. For a complete list, please refer to
188
156
the [ Upgrade etcd from v3.5 to v3.6] [ ] and the [ CHANGELOG-3.6] [ ] .
189
157
190
- ### Old Binaries Are Incompatible with New Schema Versions
158
+ Old binaries are incompatible with new schema versions
191
159
192
160
Old etcd binaries are not compatible with newer data schema versions. For example, etcd 3.5 cannot start with
193
161
data created by etcd 3.6, and etcd 3.4 cannot start with data created by either 3.5 or 3.6.
194
162
195
163
When downgrading etcd, it's important to follow the documented downgrade procedure. Simply replacing
196
164
the binary or image will result in the incompatibility issue.
197
165
198
- ### Peer Endpoints No Longer Serve Client Requests
166
+ ### Peer endpoints no longer serve client requests
199
167
200
168
Client endpoints (` --advertise-client-urls ` ) are intended to serve client requests only, while peer
201
169
endpoints (` --initial-advertise-peer-urls ` ) are intended solely for peer communication. However, due to an implementation
@@ -279,7 +247,7 @@ see [supported-platform][].
279
247
280
248
## Dependencies
281
249
282
- ### Dependency Bumping Guide
250
+ ### Dependency bumping guide
283
251
284
252
We have published an official guide on how to bump dependencies for etcd’s main branch and stable releases.
285
253
It also covers how to update the Go version. For more details, please refer to [ dependency_management] [ ] .
@@ -331,7 +299,7 @@ and transparent home for long-term stewardship and cross-project collaboration.
331
299
designation will help streamline decision-making, align roadmaps with Kubernetes needs,
332
300
and attract broader community involvement.
333
301
334
- ### New Contributors, Maintainers , and Reviewers
302
+ ### New contributors, maintainers , and reviewers
335
303
336
304
We’ve seen increasing engagement from contributors, which has resulted in the addition of three new maintainers:
337
305
@@ -349,7 +317,7 @@ We also welcome two new reviewers to the project:
349
317
We appreciate their dedication to code quality and their willingness to take on broader review responsibilities
350
318
within the community.
351
319
352
- ### New Release Team
320
+ New release team
353
321
354
322
We've formed a new release team led by [ ivanvc] [ ] and [ jmhbnz] [ ] , streamlining the release process by automating
355
323
many previously manual steps. Inspired by Kubernetes SIG Release, we've adopted several best practices, including
0 commit comments