Annual Report for SIG Instrumentation 2024 #8327
+44
−32
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,15 +12,28 @@ | |
| - Governance and leadership changes | ||
| --> | ||
|
|
||
| - `Contextual Logging` graduated to [beta](https://github.com/kubernetes/enhancements/pull/4219) | ||
| - [Usage metrics collector](https://github.com/kubernetes-sigs/usage-metrics-collector) now supports [cgroupsv2](https://github.com/kubernetes-sigs/usage-metrics-collector/pull/140) | ||
| - Introduced `Component Statusz` [alpha](https://github.com/kubernetes/enhancements/pull/4830) | ||
| - Introduced `Component Flags` [alpha](https://github.com/kubernetes/enhancements/pull/4831) | ||
| - Final draft ready for `Resource State Metrics` [alpha](https://github.com/kubernetes/enhancements/pull/4811) | ||
|
|
||
| 2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)? | ||
|
|
||
| - [kubernetes-sigs/custom-metrics-apiserver](https://github.com/kubernetes-sigs/custom-metrics-apiserver/blob/master/OWNERS) | ||
| - [kubernetes-sigs/metrics-server](https://github.com/kubernetes-sigs/metrics-server/blob/master/OWNERS) | ||
| - [kubernetes-sigs/prometheus-adapter](https://github.com/kubernetes-sigs/prometheus-adapter/blob/master/OWNERS_ALIASES) | ||
|
|
||
| 3. Did you have community-wide updates in 2024 (e.g. KubeCon talks)? | ||
|
|
||
| <!-- | ||
| Examples include links to email, slides, or recordings. | ||
| --> | ||
|
|
||
| - [SIG Instrumentation Introduction and Deep Dive (KubeCon NA '24)](https://youtu.be/IAGjj4s3F_M?si=dWCcua8XROpgqUZZ&t=0) | ||
|
|
||
| - [SIG Instrumentation Introduction and Deep Dive (KubeCon EU '24)](https://www.youtube.com/watch?v=Sx1jmIJhfyA&list=PLj6h78yzYM2N8nw1YcqqKveySH6_0VnI0&index=106) | ||
|
|
||
| 4. KEP work in 2024 (v1.30, v1.31, v1.32): | ||
| <!-- | ||
| TODO: Uncomment the following auto-generated list of KEPs, once reviewed & updated for correction. | ||
|
|
@@ -30,55 +43,54 @@ | |
| Please raise an issue in kubernetes/community, if the KEP metadata is correct but the generated list is incorrect. | ||
| --> | ||
|
|
||
| - Alpha | ||
| - [4827 - Component Statusz](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/4827-component-statusz) - v1.32 | ||
| - [4828 - Component Flagz](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/4828-component-flagz) - v1.32 | ||
|
|
||
| - Beta | ||
| - [3077 - Contextual logging](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/3077-contextual-logging) - v1.30 | ||
|
|
||
| - Stable | ||
| - [2305 - Dynamic Cardinality Enforcement](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2305-metrics-cardinality-enforcement) - v1.30 | ||
|
|
||
| ## [Subprojects](https://git.k8s.io/community/sig-instrumentation#subprojects) | ||
|
|
||
| **New in 2024:** | ||
|
|
||
| - [zpages](https://git.k8s.io/kubernetes/staging/src/k8s.io/component-base/zpages) | ||
|
|
||
| **Continuing:** | ||
|
|
||
| - custom-metrics-apiserver | ||
| - instrumentation | ||
| - instrumentation-addons | ||
| - instrumentation-tools | ||
| - klog | ||
| - kube-state-metrics | ||
| - metric-stability-framework | ||
| - metrics | ||
| - metrics-server | ||
| - prometheus-adapter | ||
| - structured-logging | ||
| - usage-metrics-collector | ||
|
|
||
| ## [Working groups](https://git.k8s.io/community/sig-instrumentation#working-groups) | ||
|
|
||
| **Continuing:** | ||
|
|
||
| - Serving | ||
| - Structured Logging | ||
|
|
||
| ## Operational | ||
|
|
||
| Operational tasks in [sig-governance.md]: | ||
|
|
||
| - [x] [README.md] reviewed for accuracy and updated if needed | ||
| - [x] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed | ||
| - [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed | ||
| - [x] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed | ||
| - [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed | ||
|
There was a problem hiding this comment. Left this unchecked since
There was a problem hiding this comment. Let's keep it unchecked to document the current status. You can always upload them and then update the report 😄 I'll defer to a SIG member for the formal lgtm. /approve (as liaison) |
||
|
|
||
|
There was a problem hiding this comment. Removed this since we do not have a CONTRIBUTION.md for sig-instrumentation. |
||
| [sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md | ||
| [README.md]: https://git.k8s.io/community/sig-instrumentation/README.md | ||
| [sigs.yaml]: https://git.k8s.io/community/sigs.yaml | ||
|
There was a problem hiding this comment. It's probably okay to keep this as is? |
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also created #8328 to add this entry
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if
zpagesas a feature should be put in the same category as, say, UMC or KSM? cc @dashpole @dgrisonnetThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually subprojects have their own repo and often have a sub-project lead. I agree this probably shouldn't be a subproject