Skip to content

Commit 9ae38a4

Browse files
authored
Merge pull request #6573 from puerco/sig-release-2021
sig-release: Add 2021 Annual Report
2 parents 47b200e + d6dcf4c commit 9ae38a4

File tree

1 file changed

+100
-69
lines changed

1 file changed

+100
-69
lines changed

sig-release/annual-report-2021.md

Lines changed: 100 additions & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -2,136 +2,165 @@
22

33
## Current initiatives
44

5-
1. What work did the SIG do this year that should be highlighted?
5+
### 1. What work did the SIG do this year that should be highlighted?
66

7-
-
8-
-
9-
-
7+
#### Release Engineering
108

11-
2. What initiatives are you working on that aren't being tracked in KEPs?
9+
After finalizing the rewrite of the release process from bash into golang,
10+
the release engineering team has been focusing its efforts on two main
11+
areas:
1212

13-
-
14-
-
15-
-
13+
1. Improving the release automation on two fronts:
14+
1. Adding new features, tests and checks to the release process which
15+
were missing from the original anago (binary verification, CVE
16+
disclosure, building from custom branches and repositories).
17+
1. Consolidating the codebases of new repositories which SIG Release
18+
brought under its responsibility. The range of new repositories we
19+
are consolidating go from critical projects (like the image promoter)
20+
to less important repositories (like downloadkubernetes.com)
21+
1. Hardening the Kubernetes Supply Chain via key efforts:
22+
1. SBOM Generation
23+
1. SLSA 3 compliance
24+
1. Artifact signing
1625

17-
3. KEP work in 2021 (1.x, 1.y, 1.z):
26+
#### Release Team
27+
28+
### 2. What initiatives are you working on that aren't being tracked in KEPs?
29+
30+
The most important change currently under development not tracked in a KEP is
31+
the new automated branch forward. Tests are currently underway and we aim to
32+
have automated forward of the release branch during code freeze by the 1.25 cycle.
33+
[A recent announcement sent to the dev mailing list](https://groups.google.com/a/kubernetes.io/g/dev/c/qbHPJjUF3s8)
34+
has more details about the plan.
35+
36+
### 3. KEP work in 2021 (1.x, 1.y, 1.z):
1837

1938
<!--
2039
In future, this will be generated from kubernetes/enhancements kep.yaml files
2140
1. with SIG as owning-sig or in participating-sigs
2241
2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
2342
-->
2443

25-
- Stable
26-
- [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable
27-
- [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable
28-
- Beta
29-
- [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta
30-
- [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta
3144
- Alpha
32-
- [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha
33-
- [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha
34-
- Pre-alpha
35-
- [$kep-number - $title](https://git.k8s.io/community/$link/README.md)
45+
- [KEP-2853 - Kubernetes repository branch rename](https://github.com/kubernetes/enhancements/blob/master/keps/sig-release/2853-k-core-branch-rename/README.md) - $milestone.stable
46+
- [KEP-3027 - SLSA Level 3 Compliance in the Kubernetes Release Process](https://github.com/kubernetes/enhancements/blob/master/keps/sig-release/3027-slsa-compliance/README.md) - $milestone.stable
47+
- [KEP-3031: Signing release artifacts](https://github.com/kubernetes/enhancements/blob/master/keps/sig-release/3031-signing-release-artifacts/README.mdhttps://git.k8s.io/community/$link/README.md) - $milestone.beta
48+
- [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta
3649

3750
## Project health
3851

3952
1. What areas and/or subprojects does your group need the most help with?
4053
Any areas with 2 or fewer OWNERs? (link to more details)
4154

42-
-
43-
-
44-
-
55+
All of the following areas are reviewed by the Release Engineering
56+
subproject, but we could always use more help here:
57+
58+
- [kubernetes-sigs/bom](https://github.com/kubernetes-sigs/bom/blob/main/OWNERS)
59+
- [kubernetes-sigs/downloadkubernetes](https://github.com/kubernetes-sigs/downloadkubernetes/blob/master/OWNERS)
60+
- [kubernetes-sigs/mdtoc](https://github.com/kubernetes-sigs/mdtoc/blob/master/OWNERS)
61+
- [kubernetes-sigs/release-notes](https://github.com/kubernetes-sigs/release-notes/blob/master/OWNERS)
62+
- [kubernetes-sigs/zeitgeist](https://github.com/kubernetes-sigs/zeitgeist/blob/master/OWNERS)
63+
- [kubernetes/repo-infra](https://github.com/kubernetes/repo-infra/blob/master/OWNERS)
4564

4665
2. What metrics/community health stats does your group care about and/or measure?
4766

48-
-
49-
-
50-
-
67+
Some data tracking efforts that SIG Release performs include monitoring release team applications,
68+
release manager activities and code commits to ensure timely release cuts in our repos.
5169

5270
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
5371
to activities or programs that provide useful context or allow easy participation?
5472

55-
-
73+
- The `CONTRIBUTING.md` was recently revamped and includes a Getting Started section with links to mentoring opportunities.
5674

5775
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
5876
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
5977

60-
-
78+
- [Release Team](https://github.com/kubernetes/sig-release/tree/master/release-team)
79+
- [Release Engineering](https://github.com/kubernetes/sig-release/tree/master/release-engineering)
6180

6281
5. Does the group have contributors from multiple companies/affiliations?
6382

64-
-
83+
- Yes, over the past two years, we've had contributors from the following companies (non-exhaustive, gathered from [here](https://k8s.devstats.cncf.io/d/55/company-prs-in-repository-groups?orgId=1&var-period_name=Last%202%20years&var-repogroups=SIG%20Release&var-repos=All&var-companies=All&var-countries=All)):
84+
- Red Hat
85+
- Cisco
86+
- Chainguard
87+
- Mattermost
88+
- Apple
89+
- SUSE
90+
- VMware
91+
- Upbound
92+
- Google
93+
- Jetstack
94+
- Kubermatic
95+
- IBM
96+
- HashiCorp
97+
- SAP
98+
- HSBC
99+
- Huawei
100+
- Intel
101+
- Autodesk
65102

66103
6. Are there ways end users/companies can contribute that they currently are not?
67104
If one of those ways is more full time support, what would they work on and why?
68105

69-
-
70-
-
106+
- We've been considering offering internships to help us round the rough edges
107+
in some repositories such as the Kuebrnetes SBOM Tool.
71108

72109
## Membership
73110

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 -->
111+
Accurate of 2022-02-14.
112+
Stats are primarily pulled from kubernetes/release, the primary repository for
113+
Release Engineering tooling/work, which serves as a reasonable representation
114+
of reviewers/approvers across SIG Release repositories.
115+
116+
- Primary Slack channel member count: 2458
117+
- Primary mailing list member count: 501
118+
- Primary meeting attendee count (estimated, if needed): 20
119+
- Primary meeting participant count (estimated, if needed): 10
120+
- Unique reviewers for SIG-owned packages (from kubernetes/release): 24
121+
- Unique approvers for SIG-owned packages (from kubernetes/release): 7
80122

81123
Include any other ways you measure group membership
82124

83125
## Subprojects
84126

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`
88-
-->
89-
90-
New in $YYYY:
91-
- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
92-
-
127+
Retired in 2021:
93128

94-
Retired in $YYYY:
95-
- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
96-
-
129+
- [Licensing](https://git.k8s.io/community/sig-release#licensing)
97130

98131
Continuing:
99-
- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
100-
-
132+
133+
- [Release Engineering](https://git.k8s.io/community/sig-release#release-engineering)
134+
- [Release Team](https://git.k8s.io/community/sig-release#release-team)
101135

102136
## Working groups
103137

104-
<!--
105-
In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
106-
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
107-
-->
138+
New in 2021:
139+
140+
- [WG Reliability](https://git.k8s.io/community/wg-reliability/) ([2021 report](https://git.k8s.io/community/wg-reliability/annual-report-2021.md))
108141

109-
New in $YYYY:
110-
- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
111-
-
142+
Retired in 2021:
112143

113-
Retired in $YYYY:
114-
- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
115-
-
144+
WG K8s Infra was converted into [SIG K8s Infra](https://git.k8s.io/community/sig-k8s-infra) in 2021.
116145

117146
Continuing:
118-
- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
119-
-
147+
148+
- [WG Reliability](https://git.k8s.io/community/wg-reliability/) ([2021 report](https://git.k8s.io/community/wg-reliability/annual-report-2021.md))
120149

121150
## Operational
122151

123152
Operational tasks in [sig-governance.md]:
124153

125-
- [ ] [README.md] reviewed for accuracy and updated if needed
126-
- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
154+
- [x] [README.md] reviewed for accuracy and updated if needed
155+
- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
127156
(or created if missing and your contributor steps and experience are different or more
128157
in-depth than the documentation listed in the general [contributor guide] and [devel] folder.)
129-
- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
130-
- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
131-
- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed
132-
- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
133-
-
134-
-
158+
- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
159+
- [x] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
160+
- [x] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed
161+
- [x] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
162+
163+
- [Hardening the Kubernetes Software Supply Chain Through Better Transparency](https://www.youtube.com/watch?v=W6hUXv66rRc) KubeCon + CloudNativeCon NA 2021
135164

136165
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-release/CONTRIBUTING.md
137166
[contributor ladder]: https://git.k8s.io/community/community-membership.md
@@ -140,4 +169,6 @@ Operational tasks in [sig-governance.md]:
140169
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
141170
[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md
142171
[devel]: https://git.k8s.io/community/contributors/devel/README.md
172+
<!-- BEGIN CUSTOM CONTENT -->
143173

174+
<!-- END CUSTOM CONTENT -->

0 commit comments

Comments
 (0)