You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[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.26
-[3085 - Pod networking ready condition](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3085-pod-conditions-for-starting-completition-of-sandbox-creation) - v1.25
26
-
-[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.25
27
30
-[3327 - CPUManager policy option to align CPUs by Socket instead of by NUMA node](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3327-align-by-socket) - v1.25
31
+
-[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.26
-[2221 - Removing dockershim from kubelet](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2221-remove-dockershim) - v1.24
38
+
29
39
- beta:
30
40
-[2712 - Pod Priority Based Graceful Node Shutdown](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2712-pod-priority-based-graceful-node-shutdown) - v1.24
-[2727 - Add gRPC probe to Pod.Spec.Container.{Liveness,Readiness,Startup}Probe](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2727-grpc-probe) - v1.24
42
+
-[2238 - Add configurable grace period to probes](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2238-liveness-probe-grace-period) - v1.25
43
+
-[2413 - seccomp by default](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2413-seccomp-by-default) - v1.25
44
+
-[3329 - Retriable and non-retriable Pod failures for Jobs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3329-retriable-and-non-retriable-failures) - v1.26
45
+
46
+
- stable
47
+
-[688 - Pod Overhead](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/688-pod-overhead) - v1.24
1. What areas and/or subprojects does your group need the most help with?
45
57
Any areas with 2 or fewer OWNERs? (link to more details)
46
58
47
-
-
48
-
-
49
-
-
59
+
- Node Problem Detector is not very active and has small participation.
60
+
- In general all areas are well covered with reviewers and approvers. However community would benefit to have clearer ownership of areas defined someplace. Ideas (https://github.com/kubernetes/community/issues/7234):
61
+
- Add more people to subdirectories as approvers
62
+
- Split more clearly between approvers and reviewers
50
63
51
64
2. What metrics/community health stats does your group care about and/or measure?
52
65
53
-
-
54
-
-
55
-
-
66
+
- Active PRs and weekly changes of PRs at weekly SIG meetings.
67
+
- Untriaged PRs, bugs - via CI group bug triage.
68
+
- It will be great to have a PR full-cycle metrics to get insights into
69
+
time to review and time to approve as well as number of iterations.
56
70
57
71
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
58
72
to activities or programs that provide useful context or allow easy participation?
59
73
60
-
-
74
+
- No, current [CONTRIBUTING.md] is not adequately covers the getting started experience for the new contributors.
75
+
- Ideas for improvements: https://github.com/kubernetes/community/issues/7223
76
+
- Also we need clearer code organization documentation for Kubernetes. This is not specific to SIG Node, but due to size, SIG Node group would likely benefit the most from it.
61
77
62
78
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
63
79
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
64
80
65
-
-
81
+
- We published the SIG Node [contributor ladder](sig-node-contributor-ladder.md)
82
+
that details requirements for reviewers/approvers.
66
83
67
84
5. Does the group have contributors from multiple companies/affiliations?
68
85
69
-
-
86
+
- The group has contributors from multiple companies/affiliations.
87
+
-[19 companies made 1+](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=y&var-metric=contributions&var-repogroup_name=SIG%20Node&var-companies=All&from=now-1y&to=now) contributions over the last year.
70
88
71
89
6. Are there ways end users/companies can contribute that they currently are not?
72
90
If one of those ways is more full time support, what would they work on and why?
73
91
74
-
-
75
-
-
92
+
- Drive dockershim deprecation and report back issues. We still see the adoption
93
+
not being very fast. It will be great to see more 3rd party tools vendors helping with migration.
94
+
- We have another potential deprecation - cgroupv1 upcoming. It will likely be
95
+
less impactful, but may need support.
96
+
- Need more feedback from end users on various deprecations and a new features.
97
+
- Can we publish surveys and check on features usage from end users?
76
98
77
99
## Membership
78
100
79
-
- Primary slack channel member count:
80
-
- Primary mailing list member count:
81
-
- Primary meeting attendee count (estimated, if needed):
82
-
- Primary meeting participant count (estimated, if needed):
83
-
- Unique reviewers for SIG-owned packages: <!--in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
84
-
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
101
+
- Primary slack channel member count: 3570 (#sig-node)
-[X] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed. Created https://github.com/kubernetes/community/issues/7234
154
+
-[X] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
155
+
-[X] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed
156
+
-[X] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
0 commit comments