|
4 | 4 |
|
5 | 5 | 1. What work did the SIG do this year that should be highlighted?
|
6 | 6 |
|
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 | +SIG-Node remains a structural piece of the Kubernetes community and the span of the work done in 2024 highlights that. |
| 8 | +As the community continues rallying behind AI use cases and identifying gaps with Kubernetes as a platform for LLM training and serving, |
| 9 | +SIG-Node made strides in multiple AI related areas. DRA structured parameters made it to beta, meaning more flexible scheduling and allocation of |
| 10 | +device resources is now possible. In 2025 there will be a lot of continued work on DRA, including enhancing drivers to be able to report device health |
| 11 | +and Kubernetes components be able to react to that, extending DRA to support advanced networking use cases, device taints and tolerations, and lots more! |
| 12 | +Outside of DRA, OCI image volume mounts have been added as alpha in 2024, allowing users to mount AI models into containers via a separate image (and one day artifact) instead |
| 13 | +of a model car or embedding it in the container image. Also, work like in-place pod resize and pod level resource limits will unlock use cases for power AI users: allowing more flexibility |
| 14 | +in pod resource limit calculation at both initialization and during runtime. |
| 15 | + |
| 16 | +Plenty of work has been being done outside of AI as well! SIG-Node remains the top SIG in KEPs progressing, moving forward on 13, 16, and 17 KEPs between 1.30, 1.31, and 1.32 respectively. |
| 17 | +Lots of progress has been made in the CPU manager: like adding support for split uncore cache, adding a policy option for restricting resrevedSystemCPUS and a new static policy for optimizing CPU alignment. |
| 18 | +We have also worked on some long awaited linux technologies like user namespaces, swap, AppArmor, ephemeral storage quotas, recursive read only mounts, and better support for supplemental groups, |
| 19 | +as well as announced feature freeze on cgroupv1. |
| 20 | + |
| 21 | +All of these features don't even begin to cover the amount of CI stabilization, bug fixes, and other work the SIG is doing. We remain a productive (albeit, occasionally overbooked) SIG. To help keep up with all |
| 22 | +of the work, we've inducted one new approver Sergey Kanzhelev, reinducted a formerly emertius approver Tim Allclair, welcomed a new SIG chair Peter Hunt, as well as began crafting a role to help KEP authors follow along the KEP process, currently called the KEP wranglers. |
14 | 23 |
|
15 | 24 | 2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
|
16 | 25 |
|
| 26 | +SIG-Node, in being so busy, always has a bottleneck of top level approvers. Any path in the kubelet could use more people who have expertise and confidence in reviewing. Please refer to our |
| 27 | +[contributor ladder](https://github.com/kubernetes/community/blob/master/sig-node/sig-node-contributor-ladder.md) to see ways to grow in the SIG! |
17 | 28 |
|
18 | 29 | 3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
|
19 | 30 |
|
20 |
| -<!-- |
21 |
| - Examples include links to email, slides, or recordings. |
22 |
| ---> |
| 31 | +- Kubecon EU 2024 [maintainers track](https://kccnceu2024.sched.com/event/1YhjL/kubernetes-sig-node-intro-and-deep-dive-dixita-narang-dawn-chen-google-matthias-bertschy-armo-peter-hunt-red-hat) |
| 32 | +- Kubecon NA 2024 [maintainers track](https://kccncna2024.sched.com/event/1hovs/sig-node-intro-and-deep-dive-sergey-kanzhelev-dawn-chen-google-mrunal-patel-red-hat) |
23 | 33 |
|
24 | 34 | 4. KEP work in 2024 (v1.30, v1.31, v1.32):
|
25 |
| -<!-- |
26 |
| - TODO: Uncomment the following auto-generated list of KEPs, once reviewed & updated for correction. |
27 |
| -
|
28 |
| - Note: This list is generated from the KEP metadata in kubernetes/enhancements repository. |
29 |
| - If you find any discrepancy in the generated list here, please check the KEP metadata. |
30 |
| - Please raise an issue in kubernetes/community, if the KEP metadata is correct but the generated list is incorrect. |
31 |
| ---> |
32 |
| - |
33 |
| -<!-- |
34 | 35 | - Alpha
|
35 |
| - - [2535 - Ensure Secret Pulled Images](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2535-ensure-secret-pulled-images) - v1.32 |
36 | 36 | - [2837 - KEP Template](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2837-pod-level-resource-spec) - v1.32
|
37 | 37 | - [2862 - Fine grained Kubelet API authorization](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2862-fine-grained-kubelet-authz) - v1.32
|
38 | 38 | - [3288 - Split Stdout and Stderr Log Stream of Container](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3288-separate-stdout-from-stderr) - v1.32
|
39 | 39 | - [3619 - Fine grained SupplementalGroups control](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3619-supplemental-groups-policy) - v1.31
|
40 |
| - - [4205 - PSI based Node Conditions](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4205-psi-metric) - v1.32 |
41 | 40 | - [4438 - Restarting sidecar containers during Pod termination](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4438-container-restart-termination) - v1.32
|
42 | 41 | - [4540 - Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4540-strict-cpu-reservation) - v1.32
|
43 | 42 | - [4580 - Deprecate & remove Kubelet RunOnce mode](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4580-deprecate-kubelet-runonce) - v1.31
|
|
108 | 107 | ## Operational
|
109 | 108 |
|
110 | 109 | Operational tasks in [sig-governance.md]:
|
111 |
| -- [ ] [README.md] reviewed for accuracy and updated if needed |
112 |
| -- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
113 |
| -- [ ] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed |
114 |
| -- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
115 |
| -- [ ] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed |
116 |
| -- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed |
| 110 | +- [x] [README.md] reviewed for accuracy and updated if needed |
| 111 | +- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
| 112 | +- [x] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed |
| 113 | +- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
| 114 | +- [x] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed |
| 115 | +- [x] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed |
117 | 116 |
|
118 | 117 |
|
119 | 118 | [CONTRIBUTING.md]: https://git.k8s.io/community/sig-node/CONTRIBUTING.md
|
|
0 commit comments