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-windows/annual-report-2021.md
+45-84Lines changed: 45 additions & 84 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,120 +3,82 @@
3
3
## Current initiatives
4
4
5
5
1. What work did the SIG do this year that should be highlighted?
6
-
7
-
-
8
-
-
9
-
-
10
-
6
+
- Implemented hostProcess container support in Kubernetes (now in beta) and pomoted adoption in multiple open source communities
7
+
-https://github.com/kubernetes-sigs/sig-windows-tools/tree/master/hostprocess - for examples of running flannel, calico, csi-proxy, kube-proxy as hostProcess containers
8
+
-https://github.com/weaveworks/kured/pull/460 - KuReD Windows support
9
+
-https://github.com/prometheus-community/windows_exporter/pull/864 - node exporter support
10
+
- Defined the `kubectl node logs` command interface.
11
+
- Made the developer UX for windows transparent with sig-windows-dev-tools.
12
+
- Defined windows operational readiness standards.
13
+
- Defined the pod OS field.
14
+
11
15
2. What initiatives are you working on that aren't being tracked in KEPs?
12
-
13
-
-
14
-
-
15
-
-
16
+
- Migration of the windows kube-proxy to KPNG.
17
+
- Migration of testgrid reporting jobs from aks-engine to cluster-api/cluster-api-provder-azure.
18
+
- Dockershim removal / validation for Windows nodes.
16
19
17
20
3. KEP work in 2021 (1.x, 1.y, 1.z):
18
-
19
-
<!--
20
-
In future, this will be generated from kubernetes/enhancements kep.yaml files
21
-
1. with SIG as owning-sig or in participating-sigs
22
-
2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
-(1.22) [1981 - Windows Privileged Container Support](https://github.com/kubernetes/enhancements/blob/master/keps/sig-windows/1981-windows-privileged-container-support/README.md)
28
+
-(1.23) [2802 -Identify Windows pods at API admission level authoritatively](https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/2802-identify-windows-pods-apiserver-admission/README.md)
29
+
- Pre-alpha (Targeting 1.24)
30
+
-[2578 - Windows Operational Readiness](https://github.com/kubernetes/enhancements/blob/master/keps/sig-windows/2578-windows-conformance/kep.yaml)
36
31
37
32
## Project health
38
33
39
34
1. What areas and/or subprojects does your group need the most help with?
40
35
Any areas with 2 or fewer OWNERs? (link to more details)
41
-
42
-
-
43
-
-
44
-
-
45
-
36
+
- csi-proxy and storage: this seems like an underserved area for windows https://github.com/kubernetes-csi/csi-proxy (meeting info is there).
46
37
2. What metrics/community health stats does your group care about and/or measure?
47
-
48
-
-
49
-
-
50
-
-
51
-
38
+
- stars for ksigs/windows specific repos
39
+
- sig-windows-dev-tools
40
+
-https://github.com/kubernetes-sigs/sig-windows-dev-tools -> up to 46, represents interest
41
+
- sig-windows-tools
42
+
- represents people trying to install windows on k8s nodes
43
+
- windows-gmsa
44
+
- represents enterprises integrating windows pods into GMSA
52
45
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
53
46
to activities or programs that provide useful context or allow easy participation?
54
-
55
-
-
56
-
47
+
- yes
57
48
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
58
49
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
59
-
60
-
-
50
+
- yes
61
51
62
52
5. Does the group have contributors from multiple companies/affiliations?
63
-
64
-
-
53
+
- yes
65
54
66
55
6. Are there ways end users/companies can contribute that they currently are not?
67
56
If one of those ways is more full time support, what would they work on and why?
68
-
69
-
-
70
-
-
57
+
- testing hostProcess implementations on several windows apps
58
+
- improving our dev tools environment to grow the community
59
+
- hardening the CSI proxy and CSI support ecosystem
60
+
- performance testing Kubernetes on Windows extensively and publishing results in cncf blog posts
71
61
72
62
## Membership
73
-
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 -->
63
+
- Primary slack channel member count: 1507
64
+
- Primary mailing list member count: 188
65
+
- Primary meeting attendee count (estimated, if needed): 10
66
+
- Primary meeting participant count (estimated, if needed): 10
67
+
- Unique reviewers for SIG-owned packages: 6
68
+
- Unique approvers for SIG-owned packages: 4
80
69
81
70
Include any other ways you measure group membership
82
71
83
72
## Subprojects
84
73
85
-
<!--
86
-
In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
87
-
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
0 commit comments