summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--sig-autoscaling/annual-report-2021.md119
1 files changed, 62 insertions, 57 deletions
diff --git a/sig-autoscaling/annual-report-2021.md b/sig-autoscaling/annual-report-2021.md
index 0ba26a1f..40bb76e8 100644
--- a/sig-autoscaling/annual-report-2021.md
+++ b/sig-autoscaling/annual-report-2021.md
@@ -4,15 +4,14 @@
1. What work did the SIG do this year that should be highlighted?
- -
- -
- -
+ - Promotion of autoscaling v2 API to GA
+ - Continued improvements of VPA via community feedback
+ - Improved extensibility of Cluster Autoscaler
2. 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
3. KEP work in 2021 (1.x, 1.y, 1.z):
@@ -23,60 +22,63 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files
-->
- Stable
- - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable
- - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable
- - Beta
- - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta
- - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta
- - Alpha
- - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha
- - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha
- - Pre-alpha
- - [$kep-number - $title](https://git.k8s.io/community/$link/README.md)
+ - [2702 - Graduate v2beta2 Autoscaling API to GA](https://git.k8s.io/enhancements/keps/sig-autoscaling/2702-graduate-hpa-api-to-GA/README.md) - $milestone.stable
+
+ - Subproject enhancements:
+ - [Support Customized Recommenders for Vertical Pod Autoscalers](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler/enhancements/3919-customized-recommender-vpa)
+ - [MinReplicas per VPA object](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler/enhancements/4566-min-replicas#kep-4566-minreplicas-per-vpa-object)
+ - [https://github.com/kubernetes/autoscaler/blob/68c984472acce69cba89d96d724d25b3c78fc4a0/cluster-autoscaler/proposals/plugable-provider-grpc.md](https://github.com/kubernetes/autoscaler/blob/68c984472acce69cba89d96d724d25b3c78fc4a0/cluster-autoscaler/proposals/plugable-provider-grpc.md)
+ - [Expander Plugin over gRPC](https://github.com/kubernetes/autoscaler/blob/66af6d1339f86e87a37d5f505109b59c729de198/cluster-autoscaler/proposals/expander-plugin-grpc.md)
## Project health
1. 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
2. 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
3. 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
4. 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
5. Does the group have contributors from multiple companies/affiliations?
- -
+ - Yes - though the core approvers are almost all from a single company.
6. 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
+ - Responding to issues - the SIG currently lacks the capacity to respond to all issues raised
## Membership
-- 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: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
-- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
+- 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<!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
+- 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<!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
Include any other ways you measure group membership
@@ -87,17 +89,21 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
-->
-New in $YYYY:
-- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
--
+New in 2021:
+
+- None
-Retired in $YYYY:
-- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
--
+Retired in 2021:
+
+- None
Continuing:
-- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
--
+
+- [horizontal-pod-autoscaler](https://github.com/kubernetes/community/blob/master/sig-autoscaling/README.md#horizontal-pod-autoscaler)
+- [vertical-pod-autoscaler](https://github.com/kubernetes/community/blob/master/sig-autoscaling/README.md#vertical-pod-autoscaler)
+- [cluster-autoscaler](https://github.com/kubernetes/community/blob/master/sig-autoscaling/README.md#cluster-autoscaler)
+- [addon-resizer](https://github.com/kubernetes/community/blob/master/sig-autoscaling/README.md#addon-resizer)
+- [scale-client](https://github.com/kubernetes/community/blob/master/sig-autoscaling/README.md#scale-client)
## Working groups
@@ -106,32 +112,32 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
-->
-New in $YYYY:
-- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
--
+New in 2021:
-Retired in $YYYY:
-- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
--
+- [WG-Batch](https://github.com/kubernetes/community/tree/master/wg-batch)
+
+Retired in 2021:
+
+- None
Continuing:
-- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
--
+
+- None
## Operational
Operational tasks in [sig-governance.md]:
-- [ ] [README.md] reviewed for accuracy and updated if needed
-- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
+- [x] [README.md] reviewed for accuracy and updated if needed
+- [x] [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:
- -
- -
+- [x] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
+- [x] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed
+- [x] 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](https://www.youtube.com/watch?v=odxPyW_rZNQ)
+ - [Kubecon NA 2021](https://www.youtube.com/watch?v=L4d7K83vq_0)
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-autoscaling/CONTRIBUTING.md
[contributor ladder]: https://git.k8s.io/community/community-membership.md
@@ -140,4 +146,3 @@ Operational tasks in [sig-governance.md]:
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md
[devel]: https://git.k8s.io/community/contributors/devel/README.md
-