|
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 | +As accelerator workloads importance grows, SIG Node **doubled down on DRA** |
| 8 | +related work. There were a few changes proposed and many improvements started in |
| 9 | +2023 will be continued in 2024. |
| 10 | + |
| 11 | +SIG Node started many alpha-level features in 2023. Specifically, **SIG Node |
| 12 | +green-lit two major features that touch Pod Lifecycle** that used to be hard to |
| 13 | +change in the past. InPlace pod update is still in alpha. Sidecar containers |
| 14 | +reached beta stage and were enabled by default in 1.29. Note that sidecar |
| 15 | +containers' importance is also partially driven by AI/ML training workloads that |
| 16 | +highly depend on reliable sidecar containers support in Kubernetes. |
| 17 | + |
| 18 | +Group is also continuing the effort of **eliminating perma-betas**. A few old beta |
| 19 | +features were GA-d and there are plans to continue this effort in 2024. |
14 | 20 |
|
15 | 21 | 2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
|
16 | 22 |
|
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 |
| ---> |
| 23 | +SIG Node delivers the highest number of KEPs in many releases despite the fact |
| 24 | +that SIG Node is heavily bottlenecked on the number of approvers. Approvers are |
| 25 | +overloaded, which creates community tension around KEPs which cannot get enough |
| 26 | +attention. This is true for global approvers, as well as subprojects like NPD. |
| 27 | +SIG Node codebase is hard to split into individual components, which makes the |
| 28 | +growing of new approvers harder. |
| 29 | + |
| 30 | +Even with the push for perma beta elimination, SIG Node still has many features |
| 31 | +that are heavily used in production, but still marked as beta. Most of the time, |
| 32 | +the work needed is not challenging or complicated, but requires a lot of effort. |
| 33 | +Help in this area will be very appreciated. |
22 | 34 |
|
23 | 35 | 3. Did you have community-wide updates in 2023 (e.g. KubeCon talks)?
|
24 | 36 |
|
25 |
| -<!-- |
26 |
| - Examples include links to email, slides, or recordings. |
27 |
| ---> |
| 37 | +- KubeCon EU 2023 [maintainers track](https://kccnceu2023.sched.com/event/1HyU4/kubernetes-sig-node-intro-and-deep-dive-sergey-kanzhelev-dawn-chen-google-derek-carr-mrunal-patel-red-hat) |
| 38 | +- KubeCon China 2023 [maintainers track](https://kccncosschn2023.sched.com/event/1PTJk/kubernetes-sigze-tao-recheng-kubernetes-sig-node-intro-and-deep-dive-paco-xu-daocloud-xiongxiong-yuan-gitlab-china) |
| 39 | +- KubeCon NA 2023 [maintainers track](https://kccncna2023.sched.com/event/1R2qd/kubernetes-sig-node-intro-and-deep-dive-sergey-kanzhelev-google-mrunal-patel-red-hat) |
28 | 40 |
|
29 | 41 | 4. KEP work in 2023 (v1.27, v1.28, v1.29):
|
30 | 42 |
|
31 | 43 | - Alpha
|
32 | 44 | - [1287 - In-place Update of Pod Resources](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1287-in-place-update-pod-resources) - v1.27
|
33 | 45 | - [2371 - cAdvisor-less, CRI-full Container and Pod Stats](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2371-cri-pod-container-stats) - v1.29
|
34 | 46 | - [2570 - Memory QoS](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2570-memory-qos) - v1.27
|
35 |
| - - [3619 - Fine grained SupplementalGroups control](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3619-supplemental-groups-policy) - v1.28 |
36 | 47 | - [3673 - KEP Template](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3673-kubelet-parallel-image-pull-limit) - v1.27
|
37 | 48 | - [3695 - Extend the PodResources API to include resources allocated by DRA](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3695-pod-resources-for-dra) - v1.27
|
38 | 49 | - [3960 - Pod lifecycle sleep action](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3960-pod-lifecycle-sleep-action) - v1.29
|
39 | 50 | - [3983 - Add support for a kubelet drop-in configuration directory](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3983-drop-in-configuration) - v1.28
|
40 | 51 | - [4033 - Discover cgroup driver from CRI](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4033-group-driver-detection-over-cri) - v1.28
|
41 |
| - - [4188 - New kubelet gRPC API with endpoint returning local pods information](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4188-kubelet-pod-readiness-api) - v1.29 |
42 | 52 | - [4191 - Splitting the Image Filesystem](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4191-split-image-filesystem) - v1.29
|
43 | 53 | - [4210 - ImageMaximumGCAge in Kubelet](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4210-max-image-gc-age) - v1.29
|
44 | 54 | - [4216 - Image pull per runtime class](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4216-image-pull-per-runtime-class) - v1.29
|
|
68 | 78 |
|
69 | 79 | **New in 2023:**
|
70 | 80 | - [resource-management](https://git.k8s.io/community/<no value>#resource-management)
|
| 81 | + |
71 | 82 | **Retired in 2023:**
|
72 | 83 | - noderesourcetopology-api
|
| 84 | + |
73 | 85 | **Continuing:**
|
74 | 86 | - ci-testing
|
75 | 87 | - cri-api
|
|
85 | 97 |
|
86 | 98 | **Retired in 2023:**
|
87 | 99 | - Multitenancy
|
| 100 | + |
88 | 101 | **Continuing:**
|
89 | 102 | - Batch
|
90 | 103 | - Policy
|
|
93 | 106 | ## Operational
|
94 | 107 |
|
95 | 108 | Operational tasks in [sig-governance.md]:
|
96 |
| -- [ ] [README.md] reviewed for accuracy and updated if needed |
97 |
| -- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
98 |
| -- [ ] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed |
99 |
| -- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
100 |
| -- [ ] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed |
101 |
| -- [ ] Meeting notes and recordings for 2023 are linked from [README.md] and updated/uploaded if needed |
| 109 | +- [X] [README.md] reviewed for accuracy and updated if needed |
| 110 | +- [X] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
| 111 | +- [X] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed |
| 112 | +- [X] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
| 113 | +- [X] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed |
| 114 | +- [X] Meeting notes and recordings for 2023 are linked from [README.md] and updated/uploaded if needed |
102 | 115 |
|
103 | 116 |
|
104 | 117 | [CONTRIBUTING.md]: https://git.k8s.io/community/sig-node/CONTRIBUTING.md
|
|
0 commit comments