Skip to content

Commit 717eb0a

Browse files
authored
Merge pull request #7188 from xing-yang/sig-storage-report-2022
Add 2022 sig-storage annual report
2 parents f9ba4b9 + 1a27771 commit 717eb0a

File tree

1 file changed

+72
-31
lines changed

1 file changed

+72
-31
lines changed

sig-storage/annual-report-2022.md

Lines changed: 72 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -4,17 +4,32 @@
44

55
1. What work did the SIG do this year that should be highlighted?
66

7-
-
8-
-
9-
-
7+
8+
- GA milestones hit
9+
- [1472 - Storage Capacity Constraints for Pod Scheduling](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1472-storage-capacity-tracking) - 1.24 blog: https://kubernetes.io/blog/2022/05/06/storage-capacity-ga/
10+
11+
- [2317 - Provide fsgroup of pod to CSI driver on mount](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2317-fsgroup-on-mount) - v1.26 blog: https://kubernetes.io/blog/2022/12/23/kubernetes-12-06-fsgroup-on-mount/
12+
13+
- [284 - Growing Persistent Volume size](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/284-enable-volume-expansion) - v1.24 blog: https://kubernetes.io/blog/2022/05/05/volume-expansion-ga/
14+
15+
- [361 - Local Ephemeral Storage Capacity Isolation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/361-local-ephemeral-storage-isolation) - v1.25 blog: https://kubernetes.io/blog/2022/09/19/local-storage-capacity-isolation-ga/
16+
17+
- [596 - Ephemeral Inline CSI Volumes](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/596-csi-inline-volumes) - v1.25 blog: https://kubernetes.io/blog/2022/08/29/csi-inline-volumes-ga/
18+
19+
- Successful progress
20+
- We continue to make great progress on CSI Migration. Core CSI Migration and CSI Migration for plugins including AWS, GCE PD, OpenStack Cinder, Azure Disk, Azure File, and vSphere all moved to GA in 2022.
1021

1122
2. What initiatives are you working on that aren't being tracked in KEPs?
1223

13-
-
14-
-
15-
-
24+
- We started a SIG-Storage Issue Triage board and weekly issue triage meeting
25+
- https://github.com/orgs/kubernetes-csi/projects/52/views/3
26+
- https://docs.google.com/document/d/1n-dXXvCbHsPfO1yrKwT1qoC80KhsxHYKbRdChdzqeXY/edit#
1627

28+
2. What initiatives are you working on that aren't being tracked in KEPs?
1729

30+
- We started a SIG-Storage Issue Triage board and weekly issue triage meeting
31+
- https://github.com/orgs/kubernetes-csi/projects/52/views/3
32+
- https://docs.google.com/document/d/1n-dXXvCbHsPfO1yrKwT1qoC80KhsxHYKbRdChdzqeXY/edit#
1833

1934
3. KEP work in 2022 (v1.24, v1.25, v1.26):
2035
- alpha:
@@ -49,44 +64,61 @@
4964
1. What areas and/or subprojects does your group need the most help with?
5065
Any areas with 2 or fewer OWNERs? (link to more details)
5166

52-
-
53-
-
54-
-
67+
- We need more contributors to help with fixing bugs and code reviewing across the board. For contributors who are interested in getting more involved in SIG-Storage, please review the [CONTRIBUTING Guide](https://github.com/kubernetes/community/blob/master/sig-storage/CONTRIBUTING.md) and come to [SIG-Storage meetings](https://github.com/kubernetes/community/tree/master/sig-storage) to find a project that you are interested in helping with. Help make code contributions and learn how storage works in Kubernetes. After you are getting familiar with the code, help with code reviews.
68+
- We now have a weekly [issue triage meeting](https://docs.google.com/document/d/1n-dXXvCbHsPfO1yrKwT1qoC80KhsxHYKbRdChdzqeXY/edit#) to discuss issues: https://github.com/orgs/kubernetes-csi/projects/52/views/3. We hope more people can join this meeting and contribute.
5569

5670
2. What metrics/community health stats does your group care about and/or measure?
5771

58-
-
59-
-
60-
-
72+
- We have been tracking features targeting every K8s release, from design, alpha, beta, to GA in our SIG meetings.
73+
- According to metrics on 3/10/2023, it shows the 7 day MA for a PR Time to Approve and Merge in sig-storage repository group is:
74+
https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&var-period=d7&var-repogroup_name=SIG%20Storage&var-apichange=All&var-size_name=All&var-kind_name=All
75+
- Median time from open to LGTM (in hours): Max 3.05 weeks, Avg 1.37 days
76+
- Median time from LGTM to approve (in hours): Max 8.25 hours, Avg 0.18 hours
77+
- Median time from approve to merge (in hours): Max 3.29 days, Avg 0.74 hours
78+
- 85th percentile time from open to LGTM (in hours): Max 13.49 weeks, Avg 1.13 weeks
79+
- 85th percentile time from LGTM to approve (in hours): Max 3.09 weeks, 10.03 hours
80+
- 85th percentile time from approve to merge (in hours): Max 2.65 weeks, 1.26 hours
81+
- Age of 7 day MA of issues by sig-storage repository group on 3/10/2023: https://k8s.devstats.cncf.io/d/15/issues-age-by-sig-and-repository-groups?orgId=1&var-period=d7&var-repogroup_name=SIG%20Storage&var-sig_name=All&var-kind_name=All&var-prio_name=All
82+
- Median time to close issue: Min 0.25 hours, Max 30.65 weeks, Avg 3.61 weeks
83+
- Average number of issues opened: Min 0.14, Max 3.14, Avg 0.88
84+
85+
- We now have a weekly [issue triage meeting](https://docs.google.com/document/d/1n-dXXvCbHsPfO1yrKwT1qoC80KhsxHYKbRdChdzqeXY/edit#) to triage issues: https://github.com/orgs/kubernetes-csi/projects/52/views/3. We hope more people can join this meeting and contribute.
6186

6287
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
6388
to activities or programs that provide useful context or allow easy participation?
6489

65-
-
90+
- Our [CONTRIBUTING.md](https://github.com/kubernetes/community/blob/master/sig-storage/CONTRIBUTING.md) has presentations, docs, and videos to help new contributors get familiar with Kubernetes Storage concepts. It also has instructions on how to get involved in SIG Storage.
91+
6692

6793
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
6894
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
6995

70-
-
96+
- We don’t have special training or documents. We just follow the contributor guide available in the K8s community. Any suggestions are welcome.
97+
7198

7299
5. Does the group have contributors from multiple companies/affiliations?
73100

74-
-
101+
- Yes.
75102

76103
6. Are there ways end users/companies can contribute that they currently are not?
77104
If one of those ways is more full time support, what would they work on and why?
78105

79-
-
80-
-
106+
- We do have a small number of contributors from end user companies. Some are working on adding new features. Any help to get them to contribute more will be great.
107+
- Here is our ask:
108+
- CSI conformance tests for CSI drivers.
109+
- Write more tests; monitor test grid health; work on test framework out of tree; enhance CSI release tools.
110+
- Doc writer to improve docs on CSI side and in general in Storage side.
111+
- We have a weekly issue triage meeting, but would appreciate help with more efficient issue triage.
112+
81113

82114
## Membership
83115

84-
- Primary slack channel member count:
85-
- Primary mailing list member count:
86-
- Primary meeting attendee count (estimated, if needed):
87-
- Primary meeting participant count (estimated, if needed):
88-
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
89-
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
116+
- Primary slack channel member count: 5373 (sig-storage), 1399 (csi)
117+
- Primary mailing list member count: 749
118+
- Primary meeting attendee count (estimated, if needed): 25
119+
- Primary meeting participant count (estimated, if needed): 25
120+
- Unique reviewers for SIG-owned packages: 36 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
121+
- Unique approvers for SIG-owned packages: 30 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
90122

91123
Include any other ways you measure group membership
92124

@@ -113,24 +145,33 @@ Include any other ways you measure group membership
113145
**Continuing:**
114146

115147
- Data Protection
148+
- KEP related work done by the DP WG is tracked in our project tracking spreadsheet and discussed in SIG Storage meetings.
149+
116150
- Multitenancy
151+
- We don’t have regular communication with Multi Tenancy WG.
152+
117153
- Policy
154+
- We don’t have regular communication with Policy WG.
155+
118156
- Structured Logging
157+
- Communication is through Structured Logging PR submission and reviews.
158+
119159

120160
## Operational
121161

122162
Operational tasks in [sig-governance.md]:
123163

124-
- [ ] [README.md] reviewed for accuracy and updated if needed
125-
- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
164+
- [x] [README.md] reviewed for accuracy and updated if needed
165+
- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
126166
(or created if missing and your contributor steps and experience are different or more
127167
in-depth than the documentation listed in the general [contributor guide] and [devel] folder.)
128-
- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
129-
- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
130-
- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed
131-
- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
132-
-
133-
-
168+
- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
169+
- [x] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
170+
- [x] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed
171+
- [x] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
172+
- Kubernetes SIG Storage Deep Dive, KubeCon Europe 2022: https://www.youtube.com/watch?v=dsEeQqRSg74
173+
- Kubernetes SIG Storage Deep Dive, KubeCon NA 2022: https://www.youtube.com/watch?v=_XXn3-yDZA0
174+
134175

135176
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-storage/CONTRIBUTING.md
136177
[contributor ladder]: https://git.k8s.io/community/community-membership.md

0 commit comments

Comments
 (0)