-
What work did the SIG do this year that should be highlighted?
- Made progress toward removing cloud provider related code from the core Kubernetes code base.
-
What initiatives are you working on that aren't being tracked in KEPs?
- Individual clouds have made significant progress on their cloud-controller-managers.
- https://github.com/kubernetes/cloud-provider-aws
- https://github.com/kubernetes/cloud-provider-gcp
- https://github.com/kubernetes/cloud-provider-openstack
- https://github.com/kubernetes/cloud-provider-vsphere
- https://github.com/kubernetes/cloud-provider-alibaba-cloud
- https://github.com/kubernetes-sigs/cloud-provider-azure
- Individual clouds have made significant progress on their cloud-controller-managers.
-
KEP work in 2021 (1.21, 1.22, 1.23):
- Leader Migration for Controller Managers #2436
- Kubelet Credential Provider #2133
- KEP for adding webhook hosting capability to the CCM framework #2699
- Stable
- Beta
- Alpha
- Pre-alpha
-
What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details)
-
What metrics/community health stats does your group care about and/or measure?
- We don't currently measure any statistics regarding community health.
- In the future, we'd like to understand better what areas our community needs help in, i.e. areas that are under-documented, areas with lots of bugs, etc.
-
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?
- We are adding a new CONTRIBUTING.md in the same PR as this report.
- As a follow-up, we need to reference CONTRIBUTING.md in our subprojects.
-
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?
- N/A (we don't have special requirements beyond the general contributor guide.
-
Does the group have contributors from multiple companies/affiliations?
- Yes, we have contributors from Amazon, Google, VMware, and others.
-
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?
- Yes, we could use help on the extraction/migration effort, including migrating tests out of the core Kubernetes repository and into each cloud-provider repository. See kubernetes/cloud-provider#25 to get started
- Primary slack channel member count: 942
- Primary mailing list member count: 240
- Primary meeting attendee count (estimated, if needed): 11
- Primary meeting participant count (estimated, if needed): 11
- Unique reviewers for SIG-owned packages: 47
- Unique approvers for SIG-owned packages: 38
See here for reviewers/approvers count method.
Continuing:
- cloud-provider-extraction-migration
- AWS Subproject Meeting
- Azure Subproject Meeting
- IBM Subproject Meeting
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: - -