|
5 | 5 |
|
6 | 6 | 1. What work did the WG do this year that should be highlighted?
|
7 | 7 |
|
8 |
| -<!-- |
9 |
| - Some example items that might be worth highlighting: |
10 |
| - - artifacts |
11 |
| - - reports |
12 |
| - - white papers |
13 |
| - - work not tracked in KEPs |
14 |
| ---> |
| 8 | +Conversion of some additional components to structured, contextual logging |
| 9 | +proceeded, most notably in the kubelet. [Contextual |
| 10 | +logging](https://github.com/kubernetes/enhancements/issues/3077) got promoted |
| 11 | +to beta in Kubernetes 1.30. |
| 12 | + |
| 13 | +Lack of support for contextual logging in client-go leads to a significant |
| 14 | +amount of log entries without context or not even using unstructured logging, |
| 15 | +[sometimes lacking information](https://github.com/kubernetes/klog/issues/414) |
| 16 | +that would identify which component the log message is about. |
| 17 | + |
| 18 | +The focus end of 2024 was on [addressing that gap in |
| 19 | +client-go](https://github.com/kubernetes/kubernetes/pull/129125), with |
| 20 | +hopefully all changes landing in Kubernetes 1.34 in 2025. |
15 | 21 |
|
16 | 22 | 2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
|
17 | 23 |
|
| 24 | +Once client-go is updated, we need to revisit components that were already |
| 25 | +converted and make them use the new client-go APIs. |
| 26 | + |
18 | 27 | ## Operational
|
19 | 28 |
|
20 | 29 | Operational tasks in [wg-governance.md]:
|
21 | 30 |
|
22 |
| -- [ ] [README.md] reviewed for accuracy and updated if needed |
23 |
| -- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed |
24 |
| -- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed |
25 |
| -- [ ] Updates provided to sponsoring SIGs in 2024 |
26 |
| - - [$sig-name](https://git.k8s.io/community/$sig-id/) |
27 |
| - - links to email, meeting notes, slides, or recordings, etc |
28 |
| - - [$sig-name](https://git.k8s.io/community/$sig-id/) |
29 |
| - - links to email, meeting notes, slides, or recordings, etc |
30 |
| - - |
| 31 | +- [x] [README.md] reviewed for accuracy and updated if needed |
| 32 | +- [x] WG leaders in [sigs.yaml] are accurate and active, and updated if needed |
| 33 | +- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed: |
| 34 | + regular meetings continue to be on hold, we discuss topics ad-hoc on Slack |
| 35 | +- [x] Updates provided to sponsoring SIGs in 2024 |
| 36 | + - KubeCon EU 2024 maintainer track presentation: ["Leverage Contextual and Structured Logging in K8s for Enhanced Monitoring"](https://kccnceu2024.sched.com/event/1YhhM/leverage-contextual-and-structured-logging-in-k8s-for-enhanced-monitoring-patrick-ohly-intel-gmbh-shivanshu-raj-shrivastava-independent-mengjiao-liu-daocloud) |
31 | 37 |
|
32 | 38 | [wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
|
33 | 39 | [README.md]: https://git.k8s.io/community/wg-structured-logging/README.md
|
|
0 commit comments