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
- Improved In-repo config support and performance.
13
+
- Support for config file sharding to better manage approval permissions.
14
+
- New monitoring stack solution that doesn’t rely on Grafana (GKE Workload Metrics + Cloud Monitoring).
15
+
- OSS-Fuzz integration.
16
+
- Private repo multitenancy (multiple private front ends).
17
+
- kubernetes/kubernetes Bazel removal GA
18
+
- Bazel removal from kubernetes/test-infra almost complete
10
19
11
20
2. What initiatives are you working on that aren't being tracked in KEPs?
12
21
13
-
-
14
-
-
15
-
-
22
+
Most of our work is not tracked via KEPs. We need to do better with bringing issues to groups and individuals to gain consensus. The current KEP process is better suited for end user features and speaks to end users more than contributors.
16
23
17
24
3. KEP work in 2021 (1.x, 1.y, 1.z):
18
25
@@ -23,36 +30,35 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files
- Google cannot continue to maintain https://monitoring.prow.k8s.io due to Grafana license change. We have switched to using Google Cloud Monitoring, but cannot make the dashboards publicly visible. We need SIG-k8s-infra to take over here or we risk losing public monitoring dashboards soon. The boskos metrics dashboard is probably the most notable loss. Currently the grafana instance is frozen.
- Not a top priority but is used by many when debugging flake.
45
53
46
54
2. What metrics/community health stats does your group care about and/or measure?
47
55
48
-
-
49
-
-
50
-
-
56
+
- Reviewers and approvers
51
57
52
58
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
53
59
to activities or programs that provide useful context or allow easy participation?
54
60
55
-
-
61
+
- No this file does not exist.
56
62
57
63
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
58
64
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
@@ -61,20 +67,19 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files
61
67
62
68
5. Does the group have contributors from multiple companies/affiliations?
63
69
64
-
-
70
+
- Yes Google and Red Hat are the majority OWNERS but we see folks from ii.co, VMware, and others.
65
71
66
72
6. Are there ways end users/companies can contribute that they currently are not?
67
73
If one of those ways is more full time support, what would they work on and why?
68
74
69
-
-
70
-
-
75
+
- We need folks to show up and stick around to climb the contributor ladder.
71
76
72
77
## Membership
73
78
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):
79
+
- Primary slack channel member count: 2117
80
+
- Primary mailing list member count: 341
81
+
- Primary meeting attendee count (estimated, if needed): 10
82
+
- Primary meeting participant count (estimated, if needed): 6
78
83
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
79
84
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
80
85
@@ -87,36 +92,12 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y
87
92
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
0 commit comments