-
What work did the SIG do this year that should be highlighted?
-
What initiatives are you working on that aren't being tracked in KEPs?
-
KEP work in 2022 (v1.24, v1.25, v1.26):
- alpha:
- 1432 - Volume Health Monitor - v1.24
- 1979 - Object Storage Support - v1.25
- 2644 - Honor Persistent Volume Reclaim Policy - v1.26
- 2924 - In-tree Storage Plugin to CSI Migration - Ceph Cephfs - v1.26
- 3107 - SecretRef field addition to NodeExpandVolume request - v1.25
- 3294 - Provision volumes from cross-namespace snapshots - v1.26
- beta:
- stable:
- 1472 - Storage Capacity Constraints for Pod Scheduling - v1.24
- 1487 - In-tree Storage Plugin to CSI Migration - AWS - v1.25
- 1488 - In-tree Storage Plugin to CSI Migration - GCE PD - v1.25
- 1489 - In-tree Storage Plugin to CSI Migration - Cinder - v1.24
- 1490 - In-tree Storage Plugin to CSI Migration - Azuredisk - v1.24
- 1491 - In-tree Storage Plugin to CSI Migration - vSphere - v1.26
- 1885 - In-tree Storage Plugin to CSI Migration - Azurefile - v1.26
- 2317 - Provide fsgroup of pod to CSI driver on mount - v1.26
- 284 - Growing Persistent Volume size - v1.24
- 361 - Local Ephemeral Storage Capacity Isolation - v1.25
- 596 - Ephemeral Inline CSI Volumes - v1.25
- 625 - In-tree Storage Plugin to CSI Migration - v1.25
-
What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details)
-
What metrics/community health stats does your group care about and/or measure?
-
Does your CONTRIBUTING.md help new contributors engage with your group specifically by pointing to activities or programs that provide useful context or allow easy participation?
-
If your group has special training, requirements for reviewers/approvers, or processes beyond the general contributor guide, does your CONTRIBUTING.md document those to help existing contributors grow throughout the contributor ladder?
-
Does the group have contributors from multiple companies/affiliations?
-
Are there ways end users/companies can contribute that they currently are not? If one of those ways is more full time support, what would they work on and why?
- Primary slack channel member count:
- Primary mailing list member count:
- Primary meeting attendee count (estimated, if needed):
- Primary meeting participant count (estimated, if needed):
- Unique reviewers for SIG-owned packages:
- Unique approvers for SIG-owned packages:
Include any other ways you measure group membership
Continuing:
- external-storage
- git-sync
- gluster-provisioner
- kubernetes-cosi
- kubernetes-csi
- mount-utils
- nfs-provisioner
- volume-populators
- volumes
Continuing:
- Data Protection
- Multitenancy
- Policy
- Structured Logging
Operational tasks in sig-governance.md:
- README.md reviewed for accuracy and updated if needed
- CONTRIBUTING.md reviewed for accuracy and updated if needed (or created if missing and your contributor steps and experience are different or more in-depth than the documentation listed in the general contributor guide and devel folder.)
- Subprojects list and linked OWNERS files in sigs.yaml reviewed for accuracy and updated if needed
- SIG leaders (chairs, tech leads, and subproject owners) in sigs.yaml are accurate and active, and updated if needed
- Meeting notes and recordings for 2022 are linked from README.md and updated/uploaded if needed
- Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - -