|
4 | 4 |
|
5 | 5 | 1. What work did the SIG do this year that should be highlighted?
|
6 | 6 |
|
7 |
| - - |
8 |
| - - |
9 |
| - - |
| 7 | + - Tracing support for the Kubernetes api-server and kubelet have graduated to beta. |
| 8 | + - We've introduced a KEP for Kubernetes control-plane component SLIs. |
| 9 | + - The metrics stability framework is being extended and now support `BETA` stability levels and auto-generated documentation. |
| 10 | + - Contextual logging has graduated to beta. |
10 | 11 |
|
11 | 12 | 2. What initiatives are you working on that aren't being tracked in KEPs?
|
12 | 13 |
|
13 |
| - - |
14 |
| - - |
15 |
| - - |
16 |
| - |
17 |
| - |
18 |
| - |
19 |
| -3. KEP work in 2022 (v1.24, v1.25, v1.26): |
20 |
| - - alpha: |
21 |
| - - [2831 - Kubelet OpenTelemetry Tracing](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2831-kubelet-tracing) - v1.25 |
22 |
| - - [3077 - Contextual logging](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/3077-contextual-logging) - v1.24 |
23 |
| - - [3466 - Kubernetes Component Health SLIs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/3466-kubernetes-component-health-slis) - v1.26 |
24 |
| - - stable: |
25 |
| - - [2845 - Deprecate klog specific flags in Kubernetes components](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components) - v1.26 |
26 |
| - |
| 14 | + - Bi-weekly triage meeting |
| 15 | + - Subprojects (see below) |
| 16 | + - Mentorship Program |
| 17 | + |
| 18 | +3. KEP work in 2022 (1.x, 1.y, 1.z): |
| 19 | + |
| 20 | +<!-- |
| 21 | +In future, this will be generated from kubernetes/enhancements kep.yaml files |
| 22 | +1. with SIG as owning-sig or in participating-sigs |
| 23 | +2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone |
| 24 | +--> |
| 25 | + - Stable |
| 26 | + - [2845 - Deprecate klog specific flags in Kubernetes components](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components) - v1.26 |
| 27 | + - [1748 - Expose metrics about resource requests and limits that represent the pod model](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/1748-pod-resource-metrics) - v1.27 |
| 28 | + |
| 29 | + - Beta |
| 30 | + - 1.27 Metrics stability enhancement |
| 31 | + - 1.27 Kubernetes component health SLIs |
| 32 | + - 1.27 Apiserver tracing |
| 33 | + - 1.27 Kubelet tracing |
| 34 | + - 1.27 Kubelet Resource Metrics Endpoint |
| 35 | + - Alpha |
| 36 | + - 1.26 Metrics stability enhancement |
| 37 | + - 1.26 Kubernetes component health SLIs |
| 38 | + - 1.25 Kubelet tracing |
27 | 39 |
|
28 | 40 | ## Project health
|
29 | 41 |
|
30 | 42 | 1. What areas and/or subprojects does your group need the most help with?
|
31 | 43 | Any areas with 2 or fewer OWNERs? (link to more details)
|
32 | 44 |
|
33 |
| - - |
34 |
| - - |
35 |
| - - |
| 45 | + - [kubernetes-sigs/prometheus-adapter](https://github.com/kubernetes-sigs/prometheus-adapter/blob/master/OWNERS_ALIASES) has 1 active approver |
| 46 | + - [kubernetes-sigs/custom-metrics-apiserver](https://github.com/kubernetes-sigs/custom-metrics-apiserver/blob/master/OWNERS) has 1 active approver |
| 47 | + - [kubernetes-sigs/metrics-server](https://github.com/kubernetes-sigs/metrics-server/blob/master/OWNERS) has 2 approvers but are both outdated |
36 | 48 |
|
37 | 49 | 2. What metrics/community health stats does your group care about and/or measure?
|
38 | 50 |
|
39 |
| - - |
40 |
| - - |
41 |
| - - |
| 51 | + - Devstats |
| 52 | + - [Review Load](https://k8s.devstats.cncf.io/d/80/pr-workload-per-sig-and-repository-chart?orgId=1&var-sigs=%22instrumentation%22&var-repo_name=kubernetes%2Fkubernetes&var-repo=kuberneteskubernetes&from=now-1y&to=now) |
| 53 | + - [Time to Approve and Merge](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&var-period=d7&var-repogroup_name=SIG%20Instrumentation&var-repo_name=kubernetes%2Fkubernetes&var-apichange=All&var-size_name=All&var-kind_name=All) |
| 54 | + - Meeting attendance |
| 55 | + - Meeting attendance is ~12 each week |
| 56 | + - Triage attendance is ~8 each week |
| 57 | + - Enhancement velocity |
| 58 | + - We have varying levels of velocity depending on our KEPs. Some graduate in successive releases while other may take more than 1 release to promote in level. |
42 | 59 |
|
43 | 60 | 3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
|
44 | 61 | to activities or programs that provide useful context or allow easy participation?
|
45 |
| - |
46 |
| - - |
| 62 | + - We certainly hope so. |
47 | 63 |
|
48 | 64 | 4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
|
49 | 65 | does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
|
50 | 66 |
|
51 |
| - - |
| 67 | + - We have a mentorship program and now have enrolled mentees/mentors. |
52 | 68 |
|
53 | 69 | 5. Does the group have contributors from multiple companies/affiliations?
|
54 | 70 |
|
55 |
| - - |
| 71 | + - Yes: Google, Red Hat, Sony, VMware, Intel, independent contributors, and more |
56 | 72 |
|
57 | 73 | 6. Are there ways end users/companies can contribute that they currently are not?
|
58 | 74 | If one of those ways is more full time support, what would they work on and why?
|
59 | 75 |
|
60 |
| - - |
61 |
| - - |
| 76 | + - SIG leads performed a [staffing and gap analysis](https://docs.google.com/document/d/1qeoP6i7GBTVJuJE1AGY5iU9dqmAOxrjqkfNQ2-rBeyI/edit#heading=h.849b7ydpl7ip) for the SIG's projects. We definitely can use more help, and need more part-time/full-time contributors. |
62 | 77 |
|
63 |
| -## Membership |
| 78 | +### Summary |
64 | 79 |
|
65 |
| -- Primary slack channel member count: |
66 |
| -- Primary mailing list member count: |
67 |
| -- Primary meeting attendee count (estimated, if needed): |
68 |
| -- Primary meeting participant count (estimated, if needed): |
69 |
| -- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> |
70 |
| -- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> |
| 80 | +- **KTLO:** 4 leads at 5%, 2 maintainers at 10% for core, 9-10 maintainers at 5% for 5 subprojects (can have overlap between roles, but need a minimum of 3-4 part-time contributors at 25%) |
| 81 | +- **Feature work:** needs significant ongoing additional investment, minimum of 2-3 FT devs or features will continue to slip |
71 | 82 |
|
72 |
| -Include any other ways you measure group membership |
| 83 | +### Details |
73 | 84 |
|
74 |
| -## [Subprojects](https://git.k8s.io/community/sig-instrumentation#subprojects) |
| 85 | +- **KTLO:** Requires two experienced part-time maintainers at 10% (e.g. 2x4h = 8h/wk) in addition to the SIG leadership (chairs/TLs @ minimum of 2h/wk) |
| 86 | + - Chairs/TLs currently perform the bulk of this work but even amongst the four of them, **do not** have 8h total weekly allocated |
| 87 | +- **Feature work:** requires significantly more investment from development and review time. |
| 88 | + - E.g. Structured logging initiative requires a minimum of 2 FT staff for the duration of feature development from beta -> GA |
| 89 | + - SIG currently owns a number of KEPs stuck in alpha/beta due to lack of dev resources: |
| 90 | + - [metric cardinality enforcement](https://github.com/kubernetes/enhancements/issues/2305) |
75 | 91 |
|
| 92 | +### Subprojects |
| 93 | + |
| 94 | +- Subprojects are currently mature/stable and mainly have KTLO needs |
| 95 | +- kube-state-metrics: 2-3 experienced maintainers at 5%, currently staffed |
| 96 | +- Metrics-server: 1 experienced maintainers at 5%, **under staffed** |
| 97 | +- Custom-metrics-apiserver: 1 experienced maintainer at 5%, currently staffed |
| 98 | +- Usage-metrics-collector: 4 experienced maintainers at 5%, currently staffed |
| 99 | +- Klog: 2 experienced maintainers at 5%, has **no current staffing** |
| 100 | +- Prometheus-adapter: 1 experienced maintainers at 5%, has **no current staffing** |
| 101 | + |
| 102 | + |
| 103 | +## Membership |
| 104 | + |
| 105 | +- Primary slack channel member count: 1,985 |
| 106 | +- Primary mailing list member count: 358 |
| 107 | +- Primary meeting attendee count (estimated, if needed): 10-12 |
| 108 | +- Primary meeting participant count (estimated, if needed): 7-8 |
| 109 | +- Unique reviewers for SIG-owned packages: 18 |
| 110 | +- Unique approvers for SIG-owned packages: 17 |
| 111 | + |
| 112 | +Include any other ways you measure group membership |
76 | 113 |
|
| 114 | +- We track active members in the SIG primarily based on devstats and meeting participation, and maintain an up-to-date roster of members in [kubernetes/org](https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-instrumentation/teams.yaml). These teams also serve as aliases for GitHub pings. |
77 | 115 |
|
78 |
| -**Continuing:** |
| 116 | +## Subprojects |
79 | 117 |
|
80 |
| - - custom-metrics-apiserver |
81 |
| - - instrumentation |
82 |
| - - instrumentation-addons |
83 |
| - - instrumentation-tools |
84 |
| - - klog |
85 |
| - - kube-state-metrics |
86 |
| - - metric-stability-framework |
87 |
| - - metrics |
88 |
| - - metrics-server |
89 |
| - - prometheus-adapter |
90 |
| - - structured-logging |
| 118 | +<!-- |
| 119 | +In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31 |
| 120 | +Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` |
| 121 | +--> |
91 | 122 |
|
| 123 | +New in 2022: |
| 124 | +- [usage-metrics-collector](https://github.com/kubernetes-sigs/usage-metrics-collector) |
92 | 125 |
|
93 |
| -## [Working groups](https://git.k8s.io/community/sig-instrumentation#working-groups) |
| 126 | +Continuing: |
| 127 | +- [instrumentation](https://github.com/kubernetes-sigs/instrumentation) |
| 128 | +- [instrumentation-addons](https://github.com/kubernetes-sigs/instrumentation-addons) |
| 129 | +- [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics) |
| 130 | +- [metrics](https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/metrics) |
| 131 | +- [custom-metrics-apiserver](https://github.com/kubernetes-sigs/custom-metrics-apiserver) |
| 132 | +- [metrics-server](https://github.com/kubernetes-sigs/metrics-server) |
| 133 | +- [prometheus-adapter](https://github.com/kubernetes-sigs/prometheus-adapter) |
| 134 | +- [klog](https://github.com/kubernetes/klog) |
| 135 | +- [structured-logging](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/component-base/logs) |
| 136 | +- [metric-stability-framework](https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/component-base/metrics) |
| 137 | +- [instrumentation-tools](https://github.com/kubernetes-sigs/instrumentation-tools) |
| 138 | +- [log-tools](https://github.com/kubernetes-sigs/logtools) |
94 | 139 |
|
| 140 | +## Working groups |
95 | 141 |
|
96 |
| -**Continuing:** |
| 142 | +<!-- |
| 143 | +In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31 |
| 144 | +Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` |
| 145 | +--> |
97 | 146 |
|
98 |
| - - Structured Logging |
| 147 | +Continuing in 2022: |
| 148 | +- WG Structured Logging |
99 | 149 |
|
100 | 150 | ## Operational
|
101 | 151 |
|
102 | 152 | Operational tasks in [sig-governance.md]:
|
103 | 153 |
|
104 |
| -- [ ] [README.md] reviewed for accuracy and updated if needed |
105 |
| -- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
| 154 | +- [x] [README.md] reviewed for accuracy and updated if needed |
| 155 | +- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
106 | 156 | (or created if missing and your contributor steps and experience are different or more
|
107 | 157 | in-depth than the documentation listed in the general [contributor guide] and [devel] folder.)
|
108 |
| -- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
109 |
| -- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed |
110 |
| -- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed |
111 |
| -- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: |
112 |
| - - |
113 |
| - - |
| 158 | +- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
| 159 | +- [x] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed |
| 160 | +- [x] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed |
| 161 | +- [x] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: |
| 162 | + - [KubeCon EU 2022 SIG Update](https://www.youtube.com/watch?v=xxG0-Ex6bjM) |
| 163 | + - [KubeCon NA 2022 SIG Update](https://www.youtube.com/watch?v=JIzrlWtAA8Y) |
| 164 | + - [Youtube Playlist for recurring meetings](https://www.youtube.com/playlist?list=PL69nYSiGNLP1tue6RXLncPTGjfnBVHP-f) |
114 | 165 |
|
115 | 166 | [CONTRIBUTING.md]: https://git.k8s.io/community/sig-instrumentation/CONTRIBUTING.md
|
116 | 167 | [contributor ladder]: https://git.k8s.io/community/community-membership.md
|
|
0 commit comments