kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SIG Cloud Provider annual report for 2021

This commit is contained in:
Nick Turner 2022-02-23 02:13:59 -08:00
parent 00e50166cc
commit a5d7305080
5 changed files with 283 additions and 68 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

213
sig-cloud-provider/CONTRIBUTING.md Normal file
View File

@ -0,0 +1,213 @@
# Contributing
Welcome to the Kubernetes SIG Cloud Provider contributing guide. We are excited
about the prospect of you joining our community!
## Before You Begin
We strongly recommend you to understand the main [Kubernetes Contributor
Guide](http://git.k8s.io/community/contributors/guide) and adhere to the
contribution rules (specially signing the CLA).
You can also check the [Contributor Cheat
Sheet](/contributors/guide/contributor-cheatsheet/), with common resources for
existing developers.
Read the [developer guide].
Please be aware that all contributions to Kubernetes require time and
commitment from project maintainers to direct and review work. This is done in
additional to many other maintainer responsibilities, and direct engagement
from maintainers is a finite resource.
### Learn about our work
* [The Future of Cloud Providers in Kubernetes](https://kubernetes.io/blog/2019/04/17/the-future-of-cloud-providers-in-kubernetes/)
* [Cloud Controller Manager](https://kubernetes.io/docs/concepts/architecture/cloud-controller/)
## Your first contribution
### Adopt an issue
Pick up an [issue] from the backlog by commenting on the issue that you would
like to work on it. Be sure to mention the author of the issue as well as the
SIG Cloud Provider members.
**Note:** Don't do this unless you will start work on the issue within a few
days of being assigned.
**Note:** GitHub only allows issues to be assigned to GitHub accounts that are
part of the organization.
**Picking your first issue**
For your first issue, we recommend picking an issue labeled with "good first
issue" from the [issue] backlog. Work with active members of the SIG to find a
suitable issue if you need help.
**Picking the right size of issue**
Be sure to pick up an issue that is appropriate to the time you are able to
commit. We recommend first time contributors start with small or medium
issues.
Following are very rough estimates, but are best effort only. They assume you
have a development environment already set up and are able to build a kubectl
binary and use it against a cluster. These estimates assume some knowledge of
Go.
- `size/S`
- simple complexity, good for novices to project (4-10 hours)
- `size/M`
- moderate complexity (10-20 hours)
- `size/L`
- high complexity (20+ hours)
- `size/XL`
- very high complexity, might require help from community members (40-80 hours)
Meta/Umbrella issues may have multiple components. By signing up for a Meta/Umbrella issue,
you are only committing to one piece of it. Let the issue author know when you have completed
some piece of it, and if you would like to continue working on it, or have it unassigned.
**Picking the right kind of issue**
Guided issues have a *type* defining the type of work to be done. Pick up an
issue that fits your experience level and interest. Documentation and
test-coverage issues typically are smaller in scope and easier to complete than
features and cleanup issues.
- `type/code-cleanup`
- Usually some refactoring or small rewrites of code.
- `type/code-documentation`
- Write `doc.go` with package overview and examples or add code comments to document
existing types and functions.
- `type/code-feature`
- Usually a new go package / library for some functionality that is requested.
Should be encapsulated in its own interfaces with thorough unit tests for the new library.
- `type/code-test-coverage`
- Audit tests for a package. Run coverage tools and also manually look at what functions
are missing unit or integration tests. Write tests for these functions.
**Provide periodic status updates**
Once you have requested an issue and it has been accepted, you will be expected
to provide periodic updates to it. Do update the issue with your status at least every
week, and publish your work to a fork so the community can see your progress and
provide early feedback.
If you find the issue is too challenging, time consuming, or you are no longer able to work on it,
this is perfectly acceptable and please let the issue author know.
If you like, you may pick up a different issue immediately or sometime in the future.
**Testing**
Look at [tests] for more information about testing.
**Summary**:
- Don't pick up an issue until you are ready to start working on it
- When you want to pick up an issue, be sure to comment to the [leads] that you
are taking the issue.
- Update the issue every week with your progress so we know it is being
actively worked on.
- There is an expectation that some time will be committed to working on the
issue each week until it is completed, or you are blocked on a maintainer.
### Meet the community
Engage with the SIG cloud provider community! Let us know who you are and how
things are going!
- In [slack][slack-messages] (signup [here][slack-signup]), @mention a
[lead][leads] and ask if there are any issues you could pick up, or let them
know what you are working on.
- Attend a sig-cloud-provider [meeting] and introduce yourself and what you are
working on.
- The sig-cloud-provider [community page] lists sig-cloud-provider [leads],
channels of [communication], and group [meeting] times.
## Information about how Features are developed
Kubernetes uses a process called a KEP (Kubernetes enhancement proposal) to
drive feature development. See [enhancements] for the most up to date
information about how enhancements are planned and developed in the Kubernetes
community.
## Escalation
### If your bug issue is stuck
If an issue isn't getting any attention and is unresolved, mention
`@kubernetes/sig-cloud-provider-bugs`.
Highlight the severity and urgency of the issue. For severe issues
escalate by contacting sig [leads] and attending the [meeting].
### If your feature request issue is stuck
If an issue isn't getting any attention and is unresolved, mention
`@kubernetes/sig-cloud-provider-feature-requests`.
If a particular issue has a high impact for you or your business,
make sure this is clear on the bug, and reach out to the sig leads
directly. Consider attending the sig meeting to discuss over video
conference.
### If your PR is stuck
It may happen that your PR seems to be stuck without clear actionable
feedback for a week or longer. A PR _associated with a bug or design
proposal_ is much less likely to be stuck than a dangling PR.
However, if it happens do the following:
- If your PR is stuck for a week or more because it has never gotten any
comments, mention `@kubernetes/sig-cloud-provider-pr-reviews` and ask for attention.
- If your PR is stuck for a week or more _after_ it got comments, but
the attention has died down. Mention the reviewer and comment with
[`PTAL`].
If you are still not able to get any attention after a couple days,
escalate to sig [leads] by mentioning them.
### If your KEP is stuck
It may happen that your KEP gets stuck without getting merged or additional
feedback. If you believe that your design is important and has been dropped, or
it is not moving forward, please add it to the sig-cloud-provider bi-weekly
meeting [agenda] and mail the [group] saying you'd like to discuss it.
### General escalation instructions
See the sig-cloud-provider [community page] for points of contact and meeting times:
- Attend the sig-cloud-provider [meeting]
- Message one of the sig leads on [slack][slack-messages] (signup [here][slack-signup])
- Send an email to the _kubernetes-cloud-provider@googlegroups.com_ [group].
## Use of [@mentions]
- `@{any lead}` solicit opinion or advice from [leads].
- `@kubernetes/sig-cloud-provider-bugs` sig-cloud-provider centric bugs.
- `@kubernetes/sig-cloud-provider-pr-reviews` triggers review of code fix PR.
- `@kubernetes/sig-cloud-provider-feature-requests` flags a feature request.
- `@kubernetes/sig-cloud-provider-proposals` flags a design proposal.
[@mentions]: https://help.github.com/articles/basic-writing-and-formatting-syntax/#mentioning-users-and-teams
[Kubernetes Basics Tutorial]: https://kubernetes.io/docs/tutorials/kubernetes-basics
[PR]: https://help.github.com/articles/creating-a-pull-request
[`PTAL`]: https://en.wiktionary.org/wiki/PTAL
[agenda]: https://docs.google.com/document/d/1OZE-ub-v6B8y-GuaWejL-vU_f9jsjBbrim4LtTfxssw/edit#
[communication]: /sig-cloud-provider/README.md#contact
[community page]: /sig-cloud-provider
[developer guide]: /contributors/devel/development.md
[enhancements]: https://github.com/kubernetes/enhancements
[group]: https://groups.google.com/forum/#!forum/kubernetes-sig-cloud-provider
[issue]: https://github.com/kubernetes/cloud-provider/issues
[leads]: /sig-cloud-provider/README.md#leadership
[meeting]: /sig-cloud-provider/README.md#meetings
[slack-messages]: https://kubernetes.slack.com/messages/sig-cloud-provider
[slack-signup]: http://slack.k8s.io/
[tests]: /contributors/devel/sig-testing/testing.md

7
sig-cloud-provider/README.md
View File

@ -23,6 +23,13 @@ The [charter](CHARTER.md) defines the scope and governance of the Cloud Provider
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
* Andrew Sy Kim (**[@andrewsykim](https://github.com/andrewsykim)**), Google
* Nick Turner (**[@nckturner](https://github.com/nckturner)**), Amazon
### Technical Leads
The Technical Leads of the SIG establish new subprojects, decommission existing
subprojects, and resolve cross-subproject technical issues and decisions.
* Andrew Sy Kim (**[@andrewsykim](https://github.com/andrewsykim)**), Google
* Walter Fender (**[@cheftako](https://github.com/cheftako)**), Google
* Nick Turner (**[@nckturner](https://github.com/nckturner)**), Amazon

122
sig-cloud-provider/annual-report-2021.md
View File

@ -4,17 +4,26 @@
1. 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.
2. 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
3. KEP work in 2021 (1.x, 1.y, 1.z):
3. KEP work in 2021 (1.21, 1.22, 1.23):
- Leader Migration for Controller Managers #2436
- https://github.com/kubernetes/enhancements/issues/2436
- Kubelet Credential Provider #2133
- https://github.com/kubernetes/enhancements/issues/2133
- KEP for adding webhook hosting capability to the CCM framework #2699
- https://github.com/kubernetes/enhancements/issues/2699
<!--
In future, this will be generated from kubernetes/enhancements kep.yaml files
@ -23,16 +32,12 @@ 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
- 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
- [2436 - Leader Migration for Controller Managers](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2436-controller-manager-leader-migration) - 1.22
- 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
- [2133 - Kubelet Credential Provider](https://git.k8s.io/community/$link/README.md) - 1.20
- Pre-alpha
- [$kep-number - $title](https://git.k8s.io/community/$link/README.md)
- [2699 - KEP for adding webhook hosting capability to the CCM framework](https://github.com/cheftako/enhancements/blob/master/keps/sig-cloud-provider/2699-add-webhook-hosting-to-ccm/README.md)
## Project health
@ -40,45 +45,53 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files
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?
2. 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.
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?
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?
-
- 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.
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]?
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]?
-
- N/A (we don't have special requirements beyond the general [contributor
guide].
5. Does the group have contributors from multiple companies/affiliations?
-
- Yes, we have contributors from Amazon, Google, VMware, and others.
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?
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?
-
-
- 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
https://github.com/kubernetes/cloud-provider/issues/25 to get started
## 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 -->
- 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
Include any other ways you measure group membership
See [here](https://gist.github.com/nckturner/cddd64bc1a56eaec836c07a24f7fecf4) for reviewers/approvers count method.
## Subprojects
@ -87,36 +100,11 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y
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))
-
- [cloud-provider-extraction-migration](https://docs.google.com/document/d/1KLsGGzNXQbsPeELCeF_q-f0h0CEGSe20xiwvcR2NlYM/edit)
- [AWS Subproject Meeting](https://docs.google.com/document/d/1-i0xQidlXnFEP9fXHWkBxqySkXwJnrGJP9OGyP2_P14/edit#)
- [Azure Subproject Meeting](https://docs.google.com/document/d/1SpxvmOgHDhnA72Z0lbhBffrfe9inQxZkU9xqlafOW9k/edit)
- [IBM Subproject Meeting](https://docs.google.com/document/d/1qd_LTu5GFaxUhSWTHigowHt3XwjJVf1L57kupj8lnwg/edit)
## Operational

2
sig-list.md
View File

@ -38,7 +38,7 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
|[Auth](sig-auth/README.md)|[auth](https://github.com/kubernetes/kubernetes/labels/sig%2Fauth)|* [Mo Khan](https://github.com/enj), VMware<br>* [Mike Danese](https://github.com/mikedanese), Google<br>* [Rita Zhang](https://github.com/ritazh), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/sig-auth)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-auth)|* Regular SIG Meeting: [Wednesdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/264572674)<br>* Secrets Store CSI Meeting: [Thursdays at 8:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/91272289538)<br>
|[Autoscaling](sig-autoscaling/README.md)|[autoscaling](https://github.com/kubernetes/kubernetes/labels/sig%2Fautoscaling)|* [Guy Templeton](https://github.com/gjtempleton), Skyscanner<br>* [Marcin Wielgus](https://github.com/mwielgus), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-autoscaling)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-autoscaling)|* Regular SIG Meeting: [Mondays at 16:00 Poland (weekly)](https://zoom.us/j/944410904)<br>
|[CLI](sig-cli/README.md)|[cli](https://github.com/kubernetes/kubernetes/labels/sig%2Fcli)|* [Katrina Verey](https://github.com/KnVerey), Shopify<br>* [Eddie Zaneski](https://github.com/eddiezane), Chainguard, Inc<br>* [Sean Sullivan](https://github.com/seans3), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cli)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cli)|* Bug Scrub: [Wednesdays at 09:00 PT (Pacific Time) (monthly)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br>* KRM Functions Subproject Meeting: [Wednesdays at 10:30 PT (Pacific Time) (biweekly)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br>* Kustomize Bug Scrub: [Wednesdays at 09:00 PT (Pacific Time) (monthly)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br>* Regular SIG Meeting: [Wednesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br>
|[Cloud Provider](sig-cloud-provider/README.md)|[cloud-provider](https://github.com/kubernetes/kubernetes/labels/sig%2Fcloud-provider)|* [Andrew Sy Kim](https://github.com/andrewsykim), Google<br>* [Walter Fender](https://github.com/cheftako), Google<br>* [Nick Turner](https://github.com/nckturner), Amazon<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cloud-provider)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cloud-provider)|* Regular SIG Meeting: [Wednesdays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/508079177?pwd=ZmEvMksxdTFTc0N1eXFLRm91QUlyUT09)<br>* (cloud-provider-extraction-migration) Weekly Sync removing the in-tree cloud providers led by @cheftako and @mcrute: [Thursdays at 13:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1KLsGGzNXQbsPeELCeF_q-f0h0CEGSe20xiwvcR2NlYM/edit)<br>* (provider-alibaba-cloud) Regular Alibaba Cloud Subproject Meeting: [Tuesdays at 12:00 UTC (monthly 2020 start date: Jan. 7th)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* (provider-aws) Regular AWS Subproject Meeting: [Fridays at 9:00 PT (Pacific Time) (biweekly 2019 start date: Jan. 11th)](https://zoom.us/my/k8ssigaws)<br>* (provider-azure) Azure Subproject Meeting: [Mondays at 18:00 PT (Pacific Time) (monthly - third Monday)](https://zoom.us/j/586836662)<br>* (provider-gcp) Regular GCP Subproject Meeting: [Thursdays at 16:00 UTC (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* (provider-ibmcloud) Regular IBM Subproject Meeting: [Wednesdays at 14:00 ET (Eastern Time) (monthly - last Wednesday every month)](https://zoom.us/j/9392903494)<br>* (provider-openstack) Regular OpenStack Subproject Meeting: [Wednesdays at 08:00 PT (Pacific Time) (biweekly starting Wednesday March 20, 2019)](https://docs.google.com/document/d/1bW3j4hFN4D8rv2LFv-DybB3gcE5ISAaOO_OpvDCgrGg/edit)<br>* (provider-vsphere) Cloud Provider vSphere monthly syncup: [Wednesdays at 09:00 PT (Pacific Time) (monthly - first Wednesday every month)](https://zoom.us/j/584244729)<br>
|[Cloud Provider](sig-cloud-provider/README.md)|[cloud-provider](https://github.com/kubernetes/kubernetes/labels/sig%2Fcloud-provider)|* [Andrew Sy Kim](https://github.com/andrewsykim), Google<br>* [Nick Turner](https://github.com/nckturner), Amazon<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cloud-provider)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cloud-provider)|* Regular SIG Meeting: [Wednesdays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/508079177?pwd=ZmEvMksxdTFTc0N1eXFLRm91QUlyUT09)<br>* (cloud-provider-extraction-migration) Weekly Sync removing the in-tree cloud providers led by @cheftako and @mcrute: [Thursdays at 13:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1KLsGGzNXQbsPeELCeF_q-f0h0CEGSe20xiwvcR2NlYM/edit)<br>* (provider-alibaba-cloud) Regular Alibaba Cloud Subproject Meeting: [Tuesdays at 12:00 UTC (monthly 2020 start date: Jan. 7th)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* (provider-aws) Regular AWS Subproject Meeting: [Fridays at 9:00 PT (Pacific Time) (biweekly 2019 start date: Jan. 11th)](https://zoom.us/my/k8ssigaws)<br>* (provider-azure) Azure Subproject Meeting: [Mondays at 18:00 PT (Pacific Time) (monthly - third Monday)](https://zoom.us/j/586836662)<br>* (provider-gcp) Regular GCP Subproject Meeting: [Thursdays at 16:00 UTC (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* (provider-ibmcloud) Regular IBM Subproject Meeting: [Wednesdays at 14:00 ET (Eastern Time) (monthly - last Wednesday every month)](https://zoom.us/j/9392903494)<br>* (provider-openstack) Regular OpenStack Subproject Meeting: [Wednesdays at 08:00 PT (Pacific Time) (biweekly starting Wednesday March 20, 2019)](https://docs.google.com/document/d/1bW3j4hFN4D8rv2LFv-DybB3gcE5ISAaOO_OpvDCgrGg/edit)<br>* (provider-vsphere) Cloud Provider vSphere monthly syncup: [Wednesdays at 09:00 PT (Pacific Time) (monthly - first Wednesday every month)](https://zoom.us/j/584244729)<br>
|[Cluster Lifecycle](sig-cluster-lifecycle/README.md)|[cluster-lifecycle](https://github.com/kubernetes/kubernetes/labels/sig%2Fcluster-lifecycle)|* [Justin Santa Barbara](https://github.com/justinsb), Google<br>* [Lubomir Ivanov](https://github.com/neolit123), VMware<br>* [Vince Prignano](https://github.com/vincepri), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cluster-lifecycle)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle)|* Regular SIG Meeting: [Tuesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/916523531?pwd=eVhPNU5IQWtBYWhmT1N4T0V6bHZFZz09)<br>* (cluster-addons) Cluster Addons meeting: [Tuesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/130096731?pwd=U3pzWloxZ0lpbEtadTZGSERRdENrZz09)<br>* (cluster-api) Cluster API office hours: [Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/861487554?pwd=dTVGVVFCblFJc0VBbkFqQlU0dHpiUT09)<br>* (cluster-api-provider-aws) Cluster API Provider AWS office hours: [Mondays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/423312508?pwd=Tk9OWnZ4WHg2T2xRek9xZXA1eFQ4dz09)<br>* (cluster-api-provider-azure) Cluster API Provider Azure office hours: [Thursdays at 08:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/566930821?pwd=N2JuRWljc3hGS3ZnVlBLTk42TFlzQT09)<br>* (cluster-api-provider-digitalocean) Cluster API Provider DigitalOcean office hours: [Thursdays at 09:00 PT (Pacific Time) (monthly, second Thursday of the month)](https://zoom.us/j/91312171751?pwd=bndnMDdJMkhySDVncjZoR1VhdFBTZz09)<br>* (cluster-api-provider-ibmcloud) Cluster API Provider IBM Cloud office hours: [Fridays at 09:00 IST (weekly)](https://zoom.us/j/9392903494)<br>* (cluster-api-provider-kubevirt) Cluster API Provider KubeVirt Syncup Meetings: [Tuesdays at 8:00 PT (Pacific Time) (weekly starting Tuesday December 7th, 2021)](https://zoom.us/j/94685513559?pwd=cnI3RUQyZ3RrckpOc1BQNDA1Q1BrZz09)<br>* (cluster-api-provider-nested) Cluster API Provider Nested Office Hours: [Tuesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/91929881559?pwd=WllxazhTUzBFN1BNWTRadTA3NGtQQT09)<br>* (cluster-api-provider-vsphere) Cluster API vSphere meeting: [Thursdays at 10:00 PT (Pacific Time) (biweekly starting Thursday June 25th, 2020)](https://zoom.us/j/92253194848?pwd=cVVVNDMxeTl1QVJPUlpvLzNSVU1JZz09)<br>* (etcdadm) etcdadm Office Hours: [Mondays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/612375927?pwd=MldxRnRSOExCVW1rbjM4ZzBSc3MvUT09)<br>* (image-builder) Image Builder office hours: [Thursdays at 08:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/807524571?pwd=WEFTeDJzeWU3bVFkcWQ0UEdZRkRCdz09)<br>* (kOps) kOps Office Hours: [Fridays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/97072789944?pwd=VVlUR3dhN2h5TEFQZHZTVVd4SnJUdz09)<br>* (kubeadm) kubeadm Office Hours: [Wednesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/179916854?pwd=dzRhbjFnRGVQRDVUVHY1a29JV2JxUT09)<br>* (minikube) minikube office hours: [Mondays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/97017029363?pwd=U3MvZ3pMMHM5eWorSjgzUnd5OEFtUT09)<br>
|[Contributor Experience](sig-contributor-experience/README.md)|[contributor-experience](https://github.com/kubernetes/kubernetes/labels/sig%2Fcontributor-experience)|* [Alison Dowdney](https://github.com/alisondy), Kasten<br>* [Bob Killen](https://github.com/mrbobbytables), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-contribex)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-contribex)|* Regular SIG Meeting: [Wednesdays at 9:00 PT (Pacific Time) (weekly alternating slack/zoom)](https://zoom.us/j/397264241?pwd=bHNnZVArNFdPaWVJMmttdko0Sktudz09)<br>* (contributor-comms) Contributor Comms - Upstream Marketing Team Meeting: [Fridays at 8:00 PT (Pacific Time) (weekly)](https://zoom.us/j/596959769?pwd=TURBNlZPb3BEWVFmbWlCYXlMVVJiUT09)<br>* (events) Office Hours European Edition (Open Q&A for end-user kubernetes related questions): [Wednesdays at 09:00 ET (Eastern Time) (monthly on 3rd Wednesday)](https://hackmd.io/@k8s/office-hours)<br>* (events) Office Hours Western Edition (Open Q&A for end-user kubernetes related questions): [Wednesdays at 12:00 ET (Eastern Time) (monthly on 3rd Wednesday)]()<br>* (github-management) GitHub Administration Subproject: [Thursdays at 09:30 PT (Pacific Time) (Monthly on 4th Thursday)](https://zoom.us/j/442435463?pwd=Rk1PWWpSSTJDaWJKdzRYb2EyTlkvZz09)<br>
|[Docs](sig-docs/README.md)|[docs](https://github.com/kubernetes/kubernetes/labels/sig%2Fdocs)|* [Divya Mohan](https://github.com/divya-mohan0209), SUSE<br>* [Jim Angel](https://github.com/jimangel), Google<br>* [Natali Vlatko](https://github.com/natalisucks), Wayfair<br>* [Rey Lejano](https://github.com/reylejano), SUSE<br>|* [Slack](https://kubernetes.slack.com/messages/sig-docs)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)|* APAC SIG Meeting: [Wednesdays at 05:30 UTC (monthly - Wednesday, after the fourth Tuesday, every month)](https://docs.google.com/document/d/1emuO4nmaQq3K8JZ9-MQeIygtrCPO9kWv7U7RzTaW4F8/edit)<br>* Korean Team Meeting: [Thursdays at 13:00 UTC (biweekly)](https://docs.google.com/document/d/1h5sMhBpPB5unJmBAS7KzDiPs-_eFQOu5o4UyHwMtFCA/edit)<br>* Localization Subgroup Meeting: [Mondays at 15:00 UTC (monthly)](https://docs.google.com/document/d/1NwO1AN8Ea2zlK8uAdaDAKf1-LZDAFvSewIfrKqfl5No/)<br>* Regular SIG Meeting: [Tuesdays at 17:30 UTC (weekly - except fourth Tuesday every month)](https://docs.google.com/document/d/1emuO4nmaQq3K8JZ9-MQeIygtrCPO9kWv7U7RzTaW4F8/edit)<br>* Spanish Team Meeting: [Tuesdays at 15:30 UTC (weekly)](https://zoom.us/j/95918289494?pwd=Wk9Oa0xZUkFXSDV5OTFoZEZsTURCZz09)<br>

7
sigs.yaml
View File

@ -763,6 +763,13 @@ sigs:
label: cloud-provider
leadership:
chairs:
- github: andrewsykim
name: Andrew Sy Kim
company: Google
- github: nckturner
name: Nick Turner
company: Amazon
tech_leads:
- github: andrewsykim
name: Andrew Sy Kim
company: Google