You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sig-autoscaling/annual-report-2021.md
+62-57Lines changed: 62 additions & 57 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,14 @@
4
4
5
5
1. What work did the SIG do this year that should be highlighted?
6
6
7
-
-
8
-
-
9
-
-
7
+
-[Promotion of autoscaling v2 API to GA.](https://github.com/kubernetes/enhancements/pull/2703)
8
+
-[Continued improvements of VPA via community feedback](https://github.com/kubernetes/autoscaler/issues/3913)
9
+
-[Improved extensibility of Cluster Autoscaler](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/proposals/plugable-provider-grpc.md)
10
10
11
11
2. What initiatives are you working on that aren't being tracked in KEPs?
12
12
13
-
-
14
-
-
15
-
-
13
+
- Continuing to improve and extend functionality of owned Subprojects
14
+
- Increasing out of band extensibility of projects via mechanisms such as gRPC providers for CA
16
15
17
16
3. KEP work in 2021 (1.x, 1.y, 1.z):
18
17
@@ -23,60 +22,63 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files
-[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
26
+
27
+
- Subproject enhancements:
28
+
-[Support Customized Recommenders for Vertical Pod Autoscalers](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler/enhancements/3919-customized-recommender-vpa)
29
+
-[MinReplicas per VPA object](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler/enhancements/4566-min-replicas#kep-4566-minreplicas-per-vpa-object)
-[Expander Plugin over gRPC](https://github.com/kubernetes/autoscaler/blob/66af6d1339f86e87a37d5f505109b59c729de198/cluster-autoscaler/proposals/expander-plugin-grpc.md)
36
32
37
33
## Project health
38
34
39
35
1. What areas and/or subprojects does your group need the most help with?
40
36
Any areas with 2 or fewer OWNERs? (link to more details)
41
37
42
-
-
43
-
-
44
-
-
38
+
- Code contributors and reviewers
39
+
- Issue triage/response
40
+
- 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.
45
41
46
42
2. What metrics/community health stats does your group care about and/or measure?
47
43
48
-
-
49
-
-
50
-
-
44
+
- Currently lacking in measurement of community health stats
45
+
- Care about growing number of contributors
46
+
- Would like to begin measuring time to merge of community PRs
51
47
52
48
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
53
49
to activities or programs that provide useful context or allow easy participation?
54
50
55
-
-
51
+
- Not currently
56
52
57
53
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
58
54
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
59
55
60
-
-
56
+
- N/A
61
57
62
58
5. Does the group have contributors from multiple companies/affiliations?
63
59
64
-
-
60
+
- 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.
65
61
66
62
6. Are there ways end users/companies can contribute that they currently are not?
67
63
If one of those ways is more full time support, what would they work on and why?
68
64
69
-
-
70
-
-
65
+
- Increased support for some cloud provider implementations for the Cluster Autoscaler. See e.g. [issues](https://github.com/kubernetes/autoscaler/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fprovider%2Faws+) and [pull requests](https://github.com/kubernetes/autoscaler/pulls?q=is%3Aopen+is%3Apr+label%3Aarea%2Fprovider%2Fhetzner) which can be queried by cloud provider for starting points. (Modify the label filter as appropriate from the above links.)
66
+
- Responding to issues - the SIG currently lacks the capacity to respond to all issues raised
71
67
72
68
## Membership
73
69
74
-
- Primary slack channel member count:
75
-
- Primary mailing list member count:
76
-
- Primary meeting attendee count (estimated, if needed):
77
-
- Primary meeting participant count (estimated, if needed):
78
-
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
79
-
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
70
+
- Primary slack channel member count: 3824
71
+
- Primary mailing list member count: 346
72
+
- Primary meeting attendee count (estimated, if needed): ~10
73
+
- Primary meeting participant count (estimated, if needed): ~6
74
+
- Unique reviewers for SIG-owned packages:
75
+
- Under k/k: 4
76
+
- SIG Subprojects Core Code: 4 to 8 depending on the project
77
+
- Cluster Autoscaler including cloud provider implementations: ~40<!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
78
+
- Unique approvers for SIG-owned packages:
79
+
- Under k/k: 4
80
+
- SIG Subprojects Core Code: 4 to 8 depending on the project
81
+
- Cluster Autoscaler including cloud provider implementations: ~40<!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
80
82
81
83
Include any other ways you measure group membership
82
84
@@ -87,17 +89,21 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y
87
89
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
0 commit comments