-
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?
- Continuing to improve and extend functionality of owned Subprojects
- Increasing out of band extensibility of projects via mechanisms such as gRPC providers for CA
-
KEP work in 2021 (1.x, 1.y, 1.z):
-
Stable
- 2702 - Graduate v2beta2 Autoscaling API to GA - $milestone.stable
-
Subproject enhancements:
-
What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details)
- Code contributors and reviewers
- Issue triage/response
- Whilst there are no areas with explicitly 2 or few owners, there are a number of areas where we have this few subject matter experts, acting as a significant bottleneck for significant changes. These currently include the core Cluster Autoscaler code, as well as the HPA controller.
-
What metrics/community health stats does your group care about and/or measure?
- Currently lacking in measurement of community health stats
- Care about growing number of contributors
- Would like to begin measuring time to merge of community PRs
-
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?
- Not currently
-
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?
- N/A
-
Does the group have contributors from multiple companies/affiliations?
- Yes - though the core approvers are almost all from a single company (Google). Other contributors/code owners are from a variety of companies, including end users (Datadog, Airbnb, Skyscanner...) and vendors (Microsoft, Red Hat, Amazon...), particularly for Cluster Autoscaler cloud provider implementations.
-
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?
- Increased support for some cloud provider implementations for the Cluster Autoscaler. See e.g. issues and pull requests which can be queried by cloud provider for starting points. (Modify the label filter as appropriate from the above links.)
- Responding to issues - the SIG currently lacks the capacity to respond to all issues raised
- Primary slack channel member count: 3824
- Primary mailing list member count: 346
- Primary meeting attendee count (estimated, if needed): ~10
- Primary meeting participant count (estimated, if needed): ~6
- Unique reviewers for SIG-owned packages:
- Under k/k: 4
- SIG Subprojects Core Code: 4 to 8 depending on the project
- Cluster Autoscaler including cloud provider implementations: ~40
- Unique approvers for SIG-owned packages:
- Under k/k: 4
- SIG Subprojects Core Code: 4 to 8 depending on the project
- Cluster Autoscaler including cloud provider implementations: ~40
Include any other ways you measure group membership
New in 2021:
- None
Retired in 2021:
- None
Continuing:
New in 2021:
Retired in 2021:
- None
Continuing:
- None
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 2021 are linked from README.md and updated/uploaded if needed
- Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - Kubecon EU 2021 - Kubecon NA 2021