Add annual report templates for 2021

generator/annual-report/sig_report.tmpl

@@ -23,16 +23,16 @@ 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
-      - [$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
-      - [$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
-      - [$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)
+     - [$kep-number - $title](https://git.k8s.io/community/$link/README.md)
 
 ## Project health
 
@@ -122,16 +122,16 @@ Continuing:
 
 Operational tasks in [sig-governance.md]:
 
-[ ] [README.md] reviewed for accuracy and updated if needed
+- [ ] [README.md] reviewed for accuracy and updated if needed
-[ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
+- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
-    (or created if missing and your contributor steps and experience are different or more
+      (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.)
+      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
+- [ ] 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
+- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
-[ ] Meeting notes and recordings for {{lastYear}} are linked from [README.md] and updated/uploaded if needed
+- [ ] Meeting notes and recordings for {{lastYear}} are linked from [README.md] and updated/uploaded if needed
-[ ] Did you have community-wide updates in {{lastYear}} (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
+- [ ] Did you have community-wide updates in {{lastYear}} (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
-    -
+      -
-    -
+      -
 
 [CONTRIBUTING.md]: https://git.k8s.io/community/{{.Dir}}/CONTRIBUTING.md
 [contributor ladder]: https://git.k8s.io/community/community-membership.md

generator/annual-report/wg_report.tmpl

@@ -46,15 +46,15 @@ Include any other ways you measure group membership
 
 Operational tasks in [wg-governance.md]:
 
-[ ] [README.md] reviewed for accuracy and updated if needed
+- [ ] [README.md] reviewed for accuracy and updated if needed
-[ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed
+- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed
-[ ] Meeting notes and recordings for {{lastYear}} are linked from [README.md] and updated/uploaded if needed
+- [ ] Meeting notes and recordings for {{lastYear}} are linked from [README.md] and updated/uploaded if needed
-[ ] Updates provided to sponsoring SIGs in {{lastYear}}
+- [ ] Updates provided to sponsoring SIGs in {{lastYear}}
-    - [$sig-name](https://git.k8s.io/community/$sig-id/)
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
-      - links to email, meeting notes, slides, or recordings, etc
+        - links to email, meeting notes, slides, or recordings, etc
-    - [$sig-name](https://git.k8s.io/community/$sig-id/)
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
-      - links to email, meeting notes, slides, or recordings, etc
+        - links to email, meeting notes, slides, or recordings, etc
-    -
+      -
 
 [wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
 [README.md]: https://git.k8s.io/community/{{.Dir}}/README.md

sig-api-machinery/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG API Machinery
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-api-machinery/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-api-machinery/README.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
+

sig-apps/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Apps
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-apps/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-apps/README.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
+

sig-architecture/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Architecture
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-architecture/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-architecture/README.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
+

sig-auth/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Auth
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-auth/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-auth/README.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
+

sig-autoscaling/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Autoscaling
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-autoscaling/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-autoscaling/README.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
+

sig-cli/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG CLI
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cli/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-cli/README.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
+

sig-cloud-provider/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Cloud Provider
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cloud-provider/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-cloud-provider/README.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
+

sig-cluster-lifecycle/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Cluster Lifecycle
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cluster-lifecycle/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-cluster-lifecycle/README.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
+

sig-contributor-experience/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Contributor Experience
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-contributor-experience/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-contributor-experience/README.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
+

sig-docs/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Docs
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-docs/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-docs/README.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
+

sig-instrumentation/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Instrumentation
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-instrumentation/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-instrumentation/README.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
+

sig-k8s-infra/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG K8s Infra
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-k8s-infra/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-k8s-infra/README.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
+

sig-multicluster/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Multicluster
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-multicluster/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-multicluster/README.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
+

sig-network/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Network
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-network/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-network/README.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
+

sig-node/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Node
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-node/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-node/README.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
+

sig-release/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Release
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-release/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-release/README.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
+

sig-scalability/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Scalability
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scalability/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-scalability/README.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
+

sig-scheduling/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Scheduling
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scheduling/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-scheduling/README.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
+

sig-security/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Security
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-security/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-security/README.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
+

sig-service-catalog/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Service Catalog
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-service-catalog/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-service-catalog/README.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
+

sig-storage/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Storage
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-storage/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-storage/README.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
+

sig-testing/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Testing
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-testing/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-testing/README.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
+

sig-ui/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG UI
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-ui/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-ui/README.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
+

sig-usability/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Usability
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-usability/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-usability/README.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
+

sig-windows/annual-report-2021.md

@@ -0,0 +1,143 @@
+# 2021 Annual Report: SIG Windows
+
+## Current initiatives
+
+1. What work did the SIG do this year that should be highlighted?
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+3. KEP work in 2021 (1.x, 1.y, 1.z):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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)
+
+## 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)
+
+   -
+   -
+   -
+
+2. What metrics/community health stats does your group care about and/or measure?
+
+   -
+   -
+   -
+
+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?
+
+   -
+
+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]?
+
+   -
+
+5. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+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?
+
+   -
+   -
+
+## 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 -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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)
+-
+
+Retired in $YYYY:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+Continuing:
+- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name)
+-
+
+## Working groups
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+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))
+-
+
+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))
+-
+
+Continuing:
+- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md))
+-
+
+## 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
+      (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:
+      -
+      -
+
+[CONTRIBUTING.md]: https://git.k8s.io/community/sig-windows/CONTRIBUTING.md
+[contributor ladder]: https://git.k8s.io/community/community-membership.md
+[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
+[README.md]: https://git.k8s.io/community/sig-windows/README.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
+

wg-api-expression/annual-report-2021.md

@@ -0,0 +1,62 @@
+# 2021 Annual Report: WG API Expression
+
+## Current initiatives
+
+1. What work did the WG do this year that should be highlighted?
+   For example, artifacts, reports, white papers produced this year.
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+## Project health
+
+1. What's the current roadmap until completion of the working group?
+
+   -
+   -
+   -
+
+2. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+3. 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?
+
+   -
+   -
+
+## 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):
+
+Include any other ways you measure group membership
+
+## Operational
+
+Operational tasks in [wg-governance.md]:
+
+- [ ] [README.md] reviewed for accuracy and updated if needed
+- [ ] WG leaders 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
+- [ ] Updates provided to sponsoring SIGs in 2021
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      -
+
+[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
+[README.md]: https://git.k8s.io/community/wg-api-expression/README.md
+[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
+

wg-data-protection/annual-report-2021.md

@@ -0,0 +1,62 @@
+# 2021 Annual Report: WG Data Protection
+
+## Current initiatives
+
+1. What work did the WG do this year that should be highlighted?
+   For example, artifacts, reports, white papers produced this year.
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+## Project health
+
+1. What's the current roadmap until completion of the working group?
+
+   -
+   -
+   -
+
+2. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+3. 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?
+
+   -
+   -
+
+## 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):
+
+Include any other ways you measure group membership
+
+## Operational
+
+Operational tasks in [wg-governance.md]:
+
+- [ ] [README.md] reviewed for accuracy and updated if needed
+- [ ] WG leaders 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
+- [ ] Updates provided to sponsoring SIGs in 2021
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      -
+
+[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
+[README.md]: https://git.k8s.io/community/wg-data-protection/README.md
+[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
+

wg-iot-edge/annual-report-2021.md

@@ -0,0 +1,62 @@
+# 2021 Annual Report: WG IoT Edge
+
+## Current initiatives
+
+1. What work did the WG do this year that should be highlighted?
+   For example, artifacts, reports, white papers produced this year.
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+## Project health
+
+1. What's the current roadmap until completion of the working group?
+
+   -
+   -
+   -
+
+2. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+3. 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?
+
+   -
+   -
+
+## 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):
+
+Include any other ways you measure group membership
+
+## Operational
+
+Operational tasks in [wg-governance.md]:
+
+- [ ] [README.md] reviewed for accuracy and updated if needed
+- [ ] WG leaders 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
+- [ ] Updates provided to sponsoring SIGs in 2021
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      -
+
+[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
+[README.md]: https://git.k8s.io/community/wg-iot-edge/README.md
+[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
+

wg-multitenancy/annual-report-2021.md

@@ -0,0 +1,62 @@
+# 2021 Annual Report: WG Multitenancy
+
+## Current initiatives
+
+1. What work did the WG do this year that should be highlighted?
+   For example, artifacts, reports, white papers produced this year.
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+## Project health
+
+1. What's the current roadmap until completion of the working group?
+
+   -
+   -
+   -
+
+2. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+3. 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?
+
+   -
+   -
+
+## 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):
+
+Include any other ways you measure group membership
+
+## Operational
+
+Operational tasks in [wg-governance.md]:
+
+- [ ] [README.md] reviewed for accuracy and updated if needed
+- [ ] WG leaders 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
+- [ ] Updates provided to sponsoring SIGs in 2021
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      -
+
+[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
+[README.md]: https://git.k8s.io/community/wg-multitenancy/README.md
+[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
+

wg-policy/annual-report-2021.md

@@ -0,0 +1,62 @@
+# 2021 Annual Report: WG Policy
+
+## Current initiatives
+
+1. What work did the WG do this year that should be highlighted?
+   For example, artifacts, reports, white papers produced this year.
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+## Project health
+
+1. What's the current roadmap until completion of the working group?
+
+   -
+   -
+   -
+
+2. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+3. 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?
+
+   -
+   -
+
+## 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):
+
+Include any other ways you measure group membership
+
+## Operational
+
+Operational tasks in [wg-governance.md]:
+
+- [ ] [README.md] reviewed for accuracy and updated if needed
+- [ ] WG leaders 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
+- [ ] Updates provided to sponsoring SIGs in 2021
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      -
+
+[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
+[README.md]: https://git.k8s.io/community/wg-policy/README.md
+[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
+

wg-reliability/annual-report-2021.md

@@ -0,0 +1,62 @@
+# 2021 Annual Report: WG Reliability
+
+## Current initiatives
+
+1. What work did the WG do this year that should be highlighted?
+   For example, artifacts, reports, white papers produced this year.
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+## Project health
+
+1. What's the current roadmap until completion of the working group?
+
+   -
+   -
+   -
+
+2. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+3. 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?
+
+   -
+   -
+
+## 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):
+
+Include any other ways you measure group membership
+
+## Operational
+
+Operational tasks in [wg-governance.md]:
+
+- [ ] [README.md] reviewed for accuracy and updated if needed
+- [ ] WG leaders 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
+- [ ] Updates provided to sponsoring SIGs in 2021
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      -
+
+[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
+[README.md]: https://git.k8s.io/community/wg-reliability/README.md
+[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
+

wg-structured-logging/annual-report-2021.md

@@ -0,0 +1,62 @@
+# 2021 Annual Report: WG Structured Logging
+
+## Current initiatives
+
+1. What work did the WG do this year that should be highlighted?
+   For example, artifacts, reports, white papers produced this year.
+
+   -
+   -
+   -
+
+2. What initiatives are you working on that aren't being tracked in KEPs?
+
+   -
+   -
+   -
+
+## Project health
+
+1. What's the current roadmap until completion of the working group?
+
+   -
+   -
+   -
+
+2. Does the group have contributors from multiple companies/affiliations?
+
+   -
+
+3. 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?
+
+   -
+   -
+
+## 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):
+
+Include any other ways you measure group membership
+
+## Operational
+
+Operational tasks in [wg-governance.md]:
+
+- [ ] [README.md] reviewed for accuracy and updated if needed
+- [ ] WG leaders 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
+- [ ] Updates provided to sponsoring SIGs in 2021
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      - [$sig-name](https://git.k8s.io/community/$sig-id/)
+        - links to email, meeting notes, slides, or recordings, etc
+      -
+
+[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
+[README.md]: https://git.k8s.io/community/wg-structured-logging/README.md
+[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
+