Skip to content

Commit c11c027

Browse files
authored
Merge pull request #7811 from jmhbnz/add-sig-etcd-report
Complete sig-etcd annual report for 2023
2 parents 94330c5 + c4bc92f commit c11c027

File tree

1 file changed

+53
-38
lines changed

1 file changed

+53
-38
lines changed

sig-etcd/annual-report-2023.md

Lines changed: 53 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -4,66 +4,81 @@
44

55
1. What work did the SIG do this year that should be highlighted?
66

7-
<!--
8-
Some example items that might be worth highlighting:
9-
- Major KEP advancement
10-
- Important initiatives that aren't tracked via KEPs
11-
- Paying down significant tech debt
12-
- Governance and leadership changes
13-
-->
7+
With etcd becoming a Kubernetes project special interest group in September 2023 over the remainder of the calendar year we:
8+
9+
- Released the first alpha for bbolt `v1.4.0`, a critical roadmap item for etcd `v3.6.0` which substantially improves logging and introduces bbolt surgery commands for working directly with storage files.
10+
- Released the first alpha for raft `v3.6.0`, a critical roadmap item for etcd `v3.6.0` which adds support for asynchronous storage writes and a number of other changes.
11+
- Donated `jpbetz/auger` to `etcd-io/auger` with subproject leads in place. With a long term home the project is now revived and being actively maintained.
12+
- In December as part of etcd `v3.5.11` we introduced new livez/readyz HTTP endpoints following design via the KEP process. The new endpoints are Kubernetes API compliant and a significant improvement over the old health endpoint. These new probes are planned to be included by kubeadm 1.31.
13+
- Released 3 patch versions for etcd stable releases between September - December 2023 .
14+
- Fixed an issue with our experimental distributed tracing feature to ensure sampling rates could be properly configured.
15+
1416

1517
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
1618

17-
<!--
18-
Note: This list is generated from the KEP metadata in kubernetes/enhancements repository.
19-
If you find any discrepancy in the generated list here, please check the KEP metadata.
20-
Please raise an issue in kubernetes/community, if the KEP metadata is correct but the generated list is incorrect.
21-
-->
19+
- An emerging risk for SIG etcd is the raft subproject which is currently operating on two primary approvers after a longstanding maintainer retired in July 2023. The two primary approvers have limited bandwidth for raft as they are also key maintainers for etcd. Over 2024 we need help growing a new maintainership for `etcd-io/raft`.
20+
21+
- The second area of concern for SIG etcd is the etcd grpc-proxy which also lacks maintainership as well as evidence for use cases. This is an area of functionality we may consider for deprecation in future if we aren't able to overcome the the maintainership challenge through a subproject lead.
22+
2223

2324
3. Did you have community-wide updates in 2023 (e.g. KubeCon talks)?
2425

25-
<!--
26-
Examples include links to email, slides, or recordings.
27-
-->
26+
The etcd project team has had talks at both Kubecon events in 2023:
2827

29-
4. KEP work in 2023 (v1.27, v1.28, v1.29):
28+
- [KubeCon Europe 2023, On the hunt for etcd data inconsistencies](https://www.youtube.com/watch?v=IIMs0EjQZHg)
29+
- [KubeCon North America 2023, Forging a stronger bond between etcd and Kubernetes](https://www.youtube.com/watch?v=6JYgBJAjpNQ)
30+
- [KubeCon North America 2023, Secrets of running etcd](https://www.youtube.com/watch?v=aJVMWcVZOPQ)
3031

32+
Additionally we held ContribFest events at both KubeCons in 2023 which have been successful in growing new contributors. In 2023 we also introduced a new fortnightly triage meeting to complement our existing fortnightly community meeting.
33+
34+
All meeting recording and maintainer track talks are available on YouTube: https://www.youtube.com/@etcdio
35+
36+
37+
4. KEP work in 2023 (v1.27, v1.28, v1.29):
3138

39+
The etcd team do not yet have KEP's tracked against specific Kubernetes versions however we do have [two open enhancements](https://github.com/kubernetes/enhancements/issues?q=is%3Aissue+etcd+label%3Asig%2Fetcd+is%3Aopen):
40+
- https://github.com/kubernetes/enhancements/issues/4326
41+
- https://github.com/kubernetes/enhancements/issues/4331
3242

3343

3444
## [Subprojects](https://git.k8s.io/community/sig-etcd#subprojects)
3545

3646

3747
**New in 2023:**
38-
- [bbolt](https://git.k8s.io/community/<no value>#bbolt)
39-
- [cetcd](https://git.k8s.io/community/<no value>#cetcd)
40-
- [dbtester](https://git.k8s.io/community/<no value>#dbtester)
41-
- [discovery.etcd.io](https://git.k8s.io/community/<no value>#discovery.etcd.io)
42-
- [discoveryserver](https://git.k8s.io/community/<no value>#discoveryserver)
43-
- [etcd](https://git.k8s.io/community/<no value>#etcd)
44-
- [etcd-play](https://git.k8s.io/community/<no value>#etcd-play)
45-
- [etcdlabs](https://git.k8s.io/community/<no value>#etcdlabs)
46-
- [gofail](https://git.k8s.io/community/<no value>#gofail)
47-
- [govanityurls](https://git.k8s.io/community/<no value>#govanityurls)
48-
- [jetcd](https://git.k8s.io/community/<no value>#jetcd)
49-
- [maintainers](https://git.k8s.io/community/<no value>#maintainers)
50-
- [protodoc](https://git.k8s.io/community/<no value>#protodoc)
51-
- [raft](https://git.k8s.io/community/<no value>#raft)
52-
- [website](https://git.k8s.io/community/<no value>#website)
53-
- [zetcd](https://git.k8s.io/community/<no value>#zetcd)
48+
- [auger](https://github.com/etcd-io/auger)
49+
50+
**Added under k8s as part of sig-etcd creation**
51+
- [bbolt](https://github.com/etcd-io/bbolt)
52+
- [dbtester](https://github.com/etcd-io/dbtester)
53+
- [discovery.etcd.io](https://github.com/etcd-io/discovery.etcd.io)
54+
- [discoveryserver](https://github.com/etcd-io/discoveryserver)
55+
- [etcd](https://github.com/etcd-io/etcd)
56+
- [etcdlabs](https://github.com/etcd-io/etcdlabs)
57+
- [gofail](https://github.com/etcd-io/gofail)
58+
- [govanityurls](https://github.com/etcd-io/govanityurls)
59+
- [jetcd](https://github.com/etcd-io/jetcd)
60+
- [protodoc](https://github.com/etcd-io/protodoc)
61+
- [raft](https://github.com/etcd-io/raft)
62+
- [website](https://github.com/etcd-io/website)
63+
64+
**Archived in 2023**
65+
- [cetcd](https://github.com/etcd-io/cetcd)
66+
- [etcd-play](https://github.com/etcd-io/etcd-play)
67+
- [maintainers](https://github.com/etcd-io/maintainers)
68+
- [zetcd](https://github.com/etcd-io/zetcd)
5469

5570
## [Working groups](https://git.k8s.io/community/sig-etcd#working-groups)
5671

5772

5873
## Operational
5974

6075
Operational tasks in [sig-governance.md]:
61-
- [ ] [README.md] reviewed for accuracy and updated if needed
62-
- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
63-
- [ ] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed
64-
- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
65-
- [ ] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed
66-
- [ ] Meeting notes and recordings for 2023 are linked from [README.md] and updated/uploaded if needed
76+
- [x] [README.md] reviewed for accuracy and updated if needed
77+
- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
78+
- [x] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed
79+
- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
80+
- [x] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed
81+
- [x] Meeting notes and recordings for 2023 are linked from [README.md] and updated/uploaded if needed
6782

6883

6984
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-etcd/CONTRIBUTING.md

0 commit comments

Comments
 (0)