Generate annual report templates for 2022

1 files changed, 126 insertions, 0 deletions

diff --git a/sig-auth/annual-report-2022.md b/sig-auth/annual-report-2022.md
new file mode 100644
index 00000000..4333b59d
--- /dev/null
+++ b/sig-auth/annual-report-2022.md
@@ -0,0 +1,126 @@
+# 2022 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 2022 (v1.24, v1.25, v1.26):
+  - alpha:
+    - [2718 - Client Executable Proxy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/2718-20210511-client-exec-proxy) - v1.26
+    - [3130 - KMS Observability](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3130-kms-observability) - v1.24
+  - stable:
+    - [2579 - PSP Replacement Policy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/2579-psp-replacement) - v1.25
+    - [2784 - CSR Duration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/2784-csr-duration) - v1.24
+
+
+## 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](https://git.k8s.io/community/sig-auth#subprojects)
+
+
+
+**New in 2022:**
+
+  - sig-auth-tools
+
+**Continuing:**
+
+  - audit-logging
+  - authenticators
+  - authorizers
+  - certificates
+  - encryption-at-rest
+  - hierarchical-namespace-controller
+  - multi-tenancy
+  - node-identity-and-isolation
+  - policy-management
+  - secrets-store-csi-driver
+  - service-accounts
+
+
+## [Working groups](https://git.k8s.io/community/sig-auth#working-groups)
+
+
+**Continuing:**
+
+ - Multitenancy
+ - Policy
+
+## 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 2022 are linked from [README.md] and updated/uploaded if needed
+- [ ] Did you have community-wide updates in 2022 (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