Merge branch 'kubernetes:master' into master
This commit is contained in:
divya-mohan0209
GitHub
commit
ce9778bf7d
|
|
@ -6,8 +6,8 @@ Welcome to the Kubernetes Community contributing guide. We are excited about the
|
|||
|
||||
We have full documentation on how to get started contributing here:
|
||||
|
||||
- [Kubernetes Contributor Guide](http://git.k8s.io/community/contributors/guide) - Main contributor documentation
|
||||
- [Contributor Cheat Sheet](./contributors/guide/contributor-cheatsheet/) - Common resources for existing developers
|
||||
- [Kubernetes Contributor Guide](https://www.kubernetes.dev/docs/guide/) - Main contributor documentation
|
||||
- [Contributor Cheat Sheet](https://www.kubernetes.dev/docs/contributor-cheatsheet/) - Common resources for existing developers
|
||||
|
||||
## Mentorship
|
||||
|
||||
|
|
|
|||
|
|
@ -40,11 +40,7 @@ aliases:
|
|||
sig-contributor-experience-leads:
|
||||
- MadhavJivrajani
|
||||
- Priyankasaggu11929
|
||||
- cblecker
|
||||
- jberkus
|
||||
- kaslin
|
||||
- mrbobbytables
|
||||
- nikhita
|
||||
- palnabarun
|
||||
sig-docs-leads:
|
||||
- divya-mohan0209
|
||||
|
|
@ -54,20 +50,26 @@ aliases:
|
|||
- reylejano
|
||||
- sftim
|
||||
- tengqm
|
||||
sig-etcd-leads:
|
||||
- ahrtr
|
||||
- jmhbnz
|
||||
- serathius
|
||||
- wenjiaswe
|
||||
sig-instrumentation-leads:
|
||||
- dashpole
|
||||
- dgrisonnet
|
||||
- ehashman
|
||||
- logicalhan
|
||||
sig-k8s-infra-leads:
|
||||
- BenTheElder
|
||||
- ameukam
|
||||
- dims
|
||||
- spiffxp
|
||||
- thockin
|
||||
- upodroid
|
||||
sig-multicluster-leads:
|
||||
- jeremyot
|
||||
- pmorie
|
||||
sig-network-leads:
|
||||
- danwinship
|
||||
- mikezappa87
|
||||
- shaneutt
|
||||
- thockin
|
||||
|
|
@ -123,8 +125,8 @@ aliases:
|
|||
- kwiesmueller
|
||||
wg-batch-leads:
|
||||
- Huang-Wei
|
||||
- ahg-g
|
||||
- endocrimes
|
||||
- mwielgus
|
||||
- soltysh
|
||||
- swatisehgal
|
||||
wg-data-protection-leads:
|
||||
|
|
@ -142,8 +144,8 @@ aliases:
|
|||
- JimBugwadia
|
||||
- rficcaglia
|
||||
wg-structured-logging-leads:
|
||||
- mengjiao-liu
|
||||
- pohly
|
||||
- serathius
|
||||
committee-code-of-conduct:
|
||||
- AnaMMedina21
|
||||
- endocrimes
|
||||
|
|
@ -161,12 +163,12 @@ aliases:
|
|||
- tabbysable
|
||||
committee-steering:
|
||||
- BenTheElder
|
||||
- cblecker
|
||||
- cpanato
|
||||
- justaugustus
|
||||
- mrbobbytables
|
||||
- pacoxu
|
||||
- palnabarun
|
||||
- tpepper
|
||||
- pohly
|
||||
- soltysh
|
||||
## BEGIN CUSTOM CONTENT
|
||||
provider-aws:
|
||||
- justinsb
|
||||
|
|
@ -181,9 +183,10 @@ aliases:
|
|||
provider-ibmcloud:
|
||||
- spzala
|
||||
provider-openstack:
|
||||
- chrigl
|
||||
- lingxiankong
|
||||
- ramineni
|
||||
- dulek
|
||||
- jichenjc
|
||||
- kayrus
|
||||
- zetaab
|
||||
provider-vmware:
|
||||
- cantbewong
|
||||
- frapposelli
|
||||
|
|
|
|||
|
|
@ -16,17 +16,34 @@ The [charter](charter.md) defines the scope and governance of the Code of Conduc
|
|||
|
||||
* Ana Margarita Medina (**[@AnaMMedina21](https://github.com/AnaMMedina21)**), Lightstep
|
||||
* Danielle Lancashire (**[@endocrimes](https://github.com/endocrimes)**), Independent
|
||||
* Hilliary Lipsig (**[@hlipsig](https://github.com/hlipsig)**), RedHat
|
||||
* Hilliary Lipsig (**[@hlipsig](https://github.com/hlipsig)**), Red Hat
|
||||
* Jeremy Rickard (**[@jeremyrickard](https://github.com/jeremyrickard)**), Microsoft
|
||||
* Xander Grzywinski (**[@salaxander](https://github.com/salaxander)**), Microsoft
|
||||
|
||||
## Emeritus Members
|
||||
|
||||
* Aeva Black (**[@AevaOnline](https://github.com/AevaOnline)**)
|
||||
* Jennifer Rondeau (**[@Bradamant3](https://github.com/Bradamant3)**)
|
||||
* Carolyn Van Slyck (**[@carolynvs](https://github.com/carolynvs)**)
|
||||
* Celeste Horgan (**[@celestehorgan](https://github.com/celestehorgan)**)
|
||||
* Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**)
|
||||
* Jason DeTiberus (**[@detiber](https://github.com/detiber)**)
|
||||
* Eric Paris (**[@eparis](https://github.com/eparis)**)
|
||||
* Jaice Singer DuMars (**[@jdumars](https://github.com/jdumars)**)
|
||||
* Karen Chu (**[@karenhchu](https://github.com/karenhchu)**)
|
||||
* Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**)
|
||||
* Paris Pittman (**[@parispittman](https://github.com/parispittman)**)
|
||||
* Tasha Drew (**[@tashimi](https://github.com/tashimi)**)
|
||||
* Tim Pepper (**[@tpepper](https://github.com/tpepper)**)
|
||||
* Vallery Lancey (**[@vllry](https://github.com/vllry)**)
|
||||
|
||||
## Contact
|
||||
- Slack: [#code-of-conduct](https://kubernetes.slack.com/messages/code-of-conduct)
|
||||
- Private Mailing List: conduct@kubernetes.io
|
||||
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/committee%2Fcode-of-conduct)
|
||||
- GitHub Teams:
|
||||
- [@kubernetes/code-of-conduct-committee](https://github.com/orgs/kubernetes/teams/code-of-conduct-committee) - General Discussion
|
||||
- Steering Committee Liaison: Tim Pepper (**[@tpepper](https://github.com/tpepper)**)
|
||||
- Steering Committee Liaison: Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**)
|
||||
|
||||
[subproject-definition]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects
|
||||
<!-- BEGIN CUSTOM CONTENT -->
|
||||
|
|
@ -41,10 +58,10 @@ Our [Incident Report Handling Procedures](incident-process.md) describes how we
|
|||
|
||||
The members and their terms are as follows:
|
||||
|
||||
### Term ends on August 23, 2023
|
||||
### Term ends on August 23, 2025
|
||||
|
||||
- Jeremy Rickard (Microsoft)
|
||||
- Jason DeTiberus (Cisco)
|
||||
- Ana Margarita Medina (Lightstep)
|
||||
|
||||
### Term ends on August 17, 2024
|
||||
|
||||
|
|
@ -54,21 +71,4 @@ The members and their terms are as follows:
|
|||
|
||||
Please see the [bootstrapping document](./bootstrapping-process.md) and [election process guidelines](election.md) for more information on how members are picked and their responsibilities.
|
||||
|
||||
## Emeritus Committee Members
|
||||
|
||||
The Code of Conduct Committee sincerely thanks our emeritus committee members for their contributions.
|
||||
|
||||
- Jaice Singer Dumars (Google)
|
||||
- Jennifer Rondeau (Stripe)
|
||||
- Carolyn Van Slyck (Microsoft)
|
||||
- Eric Paris (Red Hat)
|
||||
- Paris Pittman (Apple)
|
||||
- Aeva Black (Microsoft)
|
||||
- Tasha Drew (VMware)
|
||||
- Tim Pepper (VMware)
|
||||
- Karen Chu (Microsoft)
|
||||
- Celeste Horgan (Independent)
|
||||
- Carlos Tadeu Panato Jr. (Chainguard, Inc)
|
||||
- Vallery Lancey (Apple)
|
||||
|
||||
<!-- END CUSTOM CONTENT -->
|
||||
|
|
|
|||
|
|
@ -42,12 +42,27 @@ Nominations can be collected via any means. In the past a Google form has been u
|
|||
* Does the nominee have any experience serving on an Ethics Committee or Code of Conduct Committee? (required)
|
||||
* How has this nominee demonstrated the [eligibility for candidacy](#eligibility-for-candidacy) guidelines? (optional)
|
||||
|
||||
The nomination form must be communicated via email to [Kubernetes dev](https://groups.google.com/forum/#!forum/kubernetes-dev) mailing list.
|
||||
The nomination form must be communicated via email to [kubernetes-dev] mailing list.
|
||||
|
||||
Prior to the voting process, Steering must:
|
||||
* Vet that all nominees support the role of the code of conduct committee, i.e. maintaining a safe and inclusive space for everyone to work on Kubernetes.
|
||||
* Confirm with all nominees (that were not self nominations) that they accept the nomination.
|
||||
|
||||
#### Voting Process
|
||||
|
||||
The steering committee will setup an election and ensure that the election is open for a duration such that all members can vote.
|
||||
|
||||
Sample PR for setting up the election: https://github.com/kubernetes/community/pull/7446
|
||||
|
||||
<!-- TODO(future): Discuss the possibility of surfacing candidate bios in public -->
|
||||
<!-- TODO(future): Discuss the possibility of candidates nominating through GitHub similar to the Steering Committee Elections -->
|
||||
|
||||
#### Announcing Results
|
||||
|
||||
Once the elections are over, the steering committee will re-confirm with the winning
|
||||
candidates their intent of serving in the committee and then only announce the
|
||||
election results to [kubernetes-dev] mailing list.
|
||||
|
||||
### Maximal representation
|
||||
|
||||
Maximal representation of a single employer is `QUORUM - 1`. With a five person committee,
|
||||
|
|
@ -56,7 +71,7 @@ that limits the number of members employed by the same company to two.
|
|||
### Election Cycles
|
||||
|
||||
Election cycles are scheduled such that roughly half of the seats come up for
|
||||
re-election each year for purposes of continuity. The exact number of seats
|
||||
re-election each year for purposes of continuity. The exact number of seats
|
||||
alternates between 2 and 3. The elections by the steering committee should be
|
||||
held and announced before the previous appointments expire (typically in Aug).
|
||||
|
||||
|
|
@ -84,3 +99,5 @@ new special election will be held by the steering committee instead of filling
|
|||
with names from the previous election. Those elected will complete the remaining
|
||||
terms of the previous, dissolved, committee. With those receiving the highest
|
||||
votes receiving the longest term.
|
||||
|
||||
[kubernetes-dev]: https://groups.google.com/a/kubernetes.io/g/dev
|
||||
|
|
|
|||
|
|
@ -22,6 +22,12 @@ The Kubernetes Security Response Committee is the body that is responsible for r
|
|||
* Rita Zhang (**[@ritazh](https://github.com/ritazh)**), Microsoft
|
||||
* Tabitha Sable (**[@tabbysable](https://github.com/tabbysable)**), Datadog
|
||||
|
||||
## Emeritus Members
|
||||
|
||||
* Luke Hinds (**[@lukehinds](https://github.com/lukehinds)**)
|
||||
* Swamy Shivaganga Nagaraju (**[@swamymsft](https://github.com/swamymsft)**)
|
||||
* Tim Allclair (**[@tallclair](https://github.com/tallclair)**)
|
||||
|
||||
## Contact
|
||||
- Private Mailing List: security@kubernetes.io
|
||||
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/committee%2Fsecurity-response)
|
||||
|
|
|
|||
|
|
@ -16,18 +16,18 @@ The [charter](https://git.k8s.io/steering/charter.md) defines the scope and gove
|
|||
*Joining the [mailing list](https://groups.google.com/a/kubernetes.io/forum/#!forum/steering) for the group will typically add invites for the following meetings to your calendar.*
|
||||
* Private Steering Committee Meeting: [third Mondays at 9:30 PT (Pacific Time)](https://bit.ly/k8s-steering-wd) (monthly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:30&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting recordings](https://www.youtube.com/watch?v=YAzgJRQxsdc&list=PL69nYSiGNLP1yP1B_nd9-drjoxp0Q14qM).
|
||||
* Public Steering Committee Meeting: [first Mondays at 9:30 PT (Pacific Time)](https://bit.ly/k8s-steering-wd) (monthly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:30&tz=PT%20%28Pacific%20Time%29).
|
||||
* Public Steering Committee Meeting: [first Wednesdays at 8:00 PT (Pacific Time)](https://bit.ly/k8s-steering-wd) (monthly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=8:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting recordings](https://www.youtube.com/watch?v=YAzgJRQxsdc&list=PL69nYSiGNLP1yP1B_nd9-drjoxp0Q14qM).
|
||||
|
||||
## Members
|
||||
|
||||
* Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**), Google
|
||||
* Christoph Blecker (**[@cblecker](https://github.com/cblecker)**), Red Hat
|
||||
* Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**), Chainguard, Inc
|
||||
* Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**), Cisco
|
||||
* Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**), Google
|
||||
* Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**), DaoCloud
|
||||
* Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**), VMware
|
||||
* Tim Pepper (**[@tpepper](https://github.com/tpepper)**), VMware
|
||||
* Patrick Ohly (**[@pohly](https://github.com/pohly)**), Intel
|
||||
* Maciej Szulik (**[@soltysh](https://github.com/soltysh)**), Red Hat
|
||||
|
||||
## Contact
|
||||
- Slack: [#steering-committee](https://kubernetes.slack.com/messages/steering-committee)
|
||||
|
|
|
|||
|
|
@ -136,15 +136,40 @@ the acceptance of that SIG or Subproject.
|
|||
Additional information on the Tech Lead role can be found in
|
||||
[technical-lead.md]; within the [Chair & TL Contributor Documentation].
|
||||
|
||||
#### Subproject Owner
|
||||
#### Subproject Lead
|
||||
|
||||
**Note:** This is a generalized high-level description of the role, and the
|
||||
specifics of the subproject lead role's responsibilities and related
|
||||
processes *MUST* be defined for individual SIGs or subprojects. The process
|
||||
for becoming an Subproject Lead should be defined in the SIG charter of the
|
||||
SIG owning the subproject.
|
||||
|
||||
Subproject Leads are the technical authority for a subproject in the Kubernetes
|
||||
project. They *MUST* have demonstrated both good judgement and responsibility
|
||||
towards the health of that subproject.
|
||||
|
||||
- Number: 2+
|
||||
- Scoped to a subproject defined in [sigs.yaml]
|
||||
- Seed leads and contributors established at subproject founding
|
||||
- *SHOULD* be an escalation point for technical discussions and decisions in
|
||||
the subproject
|
||||
- Membership tracked in [sigs.yaml] via *subproject.leads* entry and scoped to a subproject
|
||||
- *MUST* set technical direction and make or approve design decisions for their subproject - either directly or through delegation
|
||||
- *MUST* mentor and guide approvers, reviewers, and contributors to the subproject.
|
||||
- *MUST* maintain components, review, shepherd and approve proposals for enhancing areas owned by the subproject
|
||||
- *MUST* actively participate in triaging issues and reviewing PRs
|
||||
- *SHOULD* be an escalation point for technical discussions and decisions in the subproject
|
||||
- *SHOULD* set milestone priorities or delegate this responsibility
|
||||
- Membership tracked in [sigs.yaml] via links to OWNERS files
|
||||
- *SHOULD* ensure a healthy process for discussion and decision making is in place.
|
||||
- *MAY* make decisions to resolve conflicts
|
||||
|
||||
#### Subproject Owner
|
||||
|
||||
- *Optional if and only if Subproject Leads are defined for the subproject*
|
||||
- Number: 2+
|
||||
- Membership tracked in [sigs.yaml] via links to OWNERS files
|
||||
- *If no Subproject Leads are defined for the subproject, the Subproject Owners will be responsible for the same duties.*
|
||||
- Scoped to a subproject defined in [sigs.yaml]
|
||||
- *MUST* actively participate in triaging issues and reviewing PRs
|
||||
- *SHOULD* mentor and guide contributors of the subproject
|
||||
- *SHOULD* help the subproject leads (if defined) in their responsibilities
|
||||
|
||||
|
||||
#### All Leads
|
||||
|
||||
|
|
@ -175,7 +200,7 @@ governance requirements, including defining more roles to sustain the group. If
|
|||
a SIG needs to change the Chair and Tech Lead position to include or remove
|
||||
duties, this needs to be approved by the Steering Committee. Newly created roles
|
||||
that don't assume any responsibility of Chair and/or Tech Lead should follow
|
||||
the governing processes in the SIGs charter.
|
||||
the governing processes in the SIGs charter.
|
||||
|
||||
Example of SIG roles created to help operations:
|
||||
|
||||
|
|
|
|||
|
|
@ -129,9 +129,9 @@ community call, and more [YouTube Guidelines].
|
|||
|
||||
#### Kubernetes Blog
|
||||
|
||||
The [Kubernetes Blog] is owned by sig-docs and operated by the [blog team].
|
||||
The [Kubernetes Blog] is owned by SIG Docs and operated by the [blog team].
|
||||
|
||||
[submit a blog post] | [2018 blog metrics]
|
||||
[submit a blog post]
|
||||
|
||||
## Misc Community Resources
|
||||
### Issues & Troubleshooting
|
||||
|
|
|
|||
|
|
@ -18,25 +18,23 @@ This team operates independently from Cloud Native Computing Foundation (CNCF) o
|
|||
|
||||
## Governance
|
||||
|
||||
The Contributor Comms subproject welcomes and encourages its members to take on leadership roles in their contributions. The group defines the areas of its work such as social media, blogging, etc. and creates associated leadership roles accordingly. Members are encouraged to pursue any interest in specific areas as contributing team members, leads, or shadows. Leadership roles are defined in the subproject’s [role handbooks](../role-handbooks/).
|
||||
The Contributor Comms subproject welcomes and encourages its members to take on leadership roles in their contributions. The group defines the areas of its work such as social media, blogging, etc. and creates associated leadership roles accordingly. Members are encouraged to pursue any interest in specific areas as contributing team members, leads, or shadows. Leadership roles are defined in the subproject’s [role handbooks](./role-handbooks/).
|
||||
|
||||
## Roles and Subproject Management
|
||||
|
||||
General subproject leadership is handled by the Contributor Comms Subproject Lead(s). Specific subproject responsibilities are also broken down into areas with their own lead roles, as defined here:
|
||||
|
||||
* Contributor Comms Subproject Lead
|
||||
* [Social Media Coordinator](../role-handbooks/Social-Media.md)
|
||||
* [Comms Tech Lead](../role-handbooks/Comms-Tech-Lead.md)
|
||||
* [Comms Event Lead](../role-handbooks/Comms-Event-Lead.md)
|
||||
* [Comms Blog Coordinator](../role-handbooks/blog-coordinator.md)
|
||||
* [Storytellers](../role-handbooks/storytellers.md) & other members
|
||||
* [Contributor Comms Subproject Lead](./role-handbooks/Subproject-Lead.md)
|
||||
* [Social Media Coordinator](./role-handbooks/Social-Media.md)
|
||||
* [Comms Tech Lead](./role-handbooks/Comms-Tech-Lead.md)
|
||||
* [Comms Blog Coordinator](./role-handbooks/blog-coordinator.md)
|
||||
* Emeritus (previous team members that we had the privilege of working with)
|
||||
|
||||
All roles can have multiple shadows and should have at least one shadow. All leads should actively recruit members and shadows for the entire team.
|
||||
|
||||
Roles are flexible and subject to change.
|
||||
|
||||
Roles are occupied or available as indicated on our [README.md](https://github.com/kubernetes/community#readme).
|
||||
Roles are occupied or available as indicated on our [README.md](https://github.com/kubernetes/community/tree/master/communication/contributor-comms#readme).
|
||||
|
||||
### Decision Making
|
||||
|
||||
|
|
|
|||
|
|
@ -1,20 +1,20 @@
|
|||
# See the OWNERS docs at https://go.k8s.io/owners
|
||||
|
||||
reviewers:
|
||||
- Atharva-Shinde
|
||||
- AvineshTripathi
|
||||
- chris-short
|
||||
- fsmunoz
|
||||
- imnmo
|
||||
- kaslin
|
||||
- SD-13
|
||||
approvers:
|
||||
- Atharva-Shinde
|
||||
- AvineshTripathi
|
||||
- chris-short
|
||||
- fsmunoz
|
||||
- imnmo
|
||||
- kaslin
|
||||
- SD-13
|
||||
emeritus_approvers:
|
||||
- Atharva-Shinde
|
||||
- imnmo
|
||||
- Pensu
|
||||
- mbbroberg
|
||||
- parispittman
|
||||
|
|
|
|||
|
|
@ -34,6 +34,10 @@ To find out what projects we're currently working on and explore what you could
|
|||
* Reach out to us on the #sig-contribex-comms channel on the Kubernetes slack ([slack.k8s.io](http://slack.k8s.io)).
|
||||
* Join our [mailing-list]
|
||||
|
||||
As with all contribution to Kubernetes, adhere to the [code of conduct], values, and principles of the project.
|
||||
|
||||
**NOTE**
|
||||
|
||||
[meetings]: /sig-contributor-experience#contributor-comms
|
||||
[calendar]: https://www.kubernetes.dev/resources/calendar/
|
||||
[mailing-list]: https://groups.google.com/g/kubernetes-sig-contribex
|
||||
|
|
@ -50,3 +54,4 @@ To find out what projects we're currently working on and explore what you could
|
|||
[area/contributor-comms]: https://github.com/kubernetes/community/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fcontributor-comms
|
||||
[Twitter]: https://twitter.com/K8sContributors/
|
||||
[Mastodon]: https://hachyderm.io/@K8sContributors
|
||||
[code of conduct]: https://github.com/kubernetes/community/blob/master/code-of-conduct.md
|
||||
|
|
@ -11,38 +11,42 @@ To use the bot, the user must be a member of the Slack 'sig-contributor-comms' g
|
|||
|
||||
To allow the bot to send messages to a channel, it must first be added to the channel. Before adding it, you need to make sure that the bot has already joined the channel. Although the bot is added to most of the channels, it might still be necessary to add it to a new channel. Follow the steps below to do so.
|
||||
|
||||
|
||||
1. Go to the 'More' option in the top left side and then go to 'Apps'
|
||||
<img src="./announcementbot-images/add-bot-to-channel/step-1.png">
|
||||
|
||||
|
||||
|
||||
2. That will take you to the apps page & choose 'Announcement bot' in this page
|
||||
<img src="./announcementbot-images/add-bot-to-channel/step-2.png">
|
||||
|
||||
|
||||
|
||||
3. Now, slack will take you to a DM page with the bot. Click on the title of the bot at the top of this page
|
||||
<img src="./announcementbot-images/add-bot-to-channel/step-3.png">
|
||||
|
||||
|
||||
|
||||
4. In the pop-up click on 'Add this app to a channel' & enter the channel name. This will have add the bot to the specified channel
|
||||
<img src="./announcementbot-images/add-bot-to-channel/step-4.png>
|
||||
|
||||
|
||||
|
||||
|
||||
## Pushing announcements through the bot
|
||||
|
||||
1. From any page on slack, find the '+' button called as "Attachments & shortcuts" in the text box
|
||||
<img src="./announcementbot-images/make-announcement/step-1.png">
|
||||
|
||||
|
||||
|
||||
2. In the options displayed, click on 'Browse all shortcuts'
|
||||
<img src="./announcementbot-images/make-announcement/step-2.png">
|
||||
|
||||
|
||||
|
||||
3. In the following page choose 'Announcement bot'
|
||||
<img src="./announcementbot-images/make-announcement/step-3.png">
|
||||
|
||||
|
||||
|
||||
4. In the options displayed for 'Announcement bot' click on 'Post message' which open the message form
|
||||
<img src="./announcementbot-images/make-announcement/step-4.png">
|
||||
|
||||
5. In the form, choose the channel(s), write the message that needs to be sent and click on 'submit' buttom.
|
||||
The keyboard here might not support slack emoji search (with `:`) The workaround for this is to copy emojis
|
||||
<img src="./announcementbot-images/make-announcement/step-5.png">
|
||||
|
||||
|
||||
5. In the form, choose the channel(s), write the message that needs to be sent and click on 'submit' bottom.
|
||||
|
||||
The keyboard here might not support slack emoji search (with `:`) The workaround for this is to copy emojis
|
||||
|
||||
|
||||
|
|
@ -1,5 +1,7 @@
|
|||
# Blogging resources
|
||||
|
||||
Contributor Comms depends on great storytelling to get the message out about our amazing community. We help Kubernetes contributors hear the latest news in the most entertaining ways. This can be done through words and visuals.
|
||||
|
||||
We have collected some information to get anyone started. If you're looking to get started blogging on the kubernetes.dev blog, this page contains a list of resources available to help you be successful.
|
||||
|
||||
## [Blog guidelines](./blog-guidelines.md)
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ existing tools and processes, and in general tips and suggestions on
|
|||
how to collaborate.
|
||||
|
||||
Other types of content, like Kubernetes capabilities, tutorials, and
|
||||
technical articles, are better suited for the [SIG-Docs blogging
|
||||
technical articles, are better suited for the [SIG Docs blogging
|
||||
initiative](/sig-docs/blog-subproject/README.md).
|
||||
|
||||
## Where to publish
|
||||
|
|
@ -85,6 +85,9 @@ follows:
|
|||
guide](https://kubernetes.io/docs/contribute/style/style-guide/):
|
||||
these guidelines can help in improving the readability of your
|
||||
article, especially in terms of the use of Kubernetes terminology.
|
||||
You can also read
|
||||
[Submitting blog posts and case studies](https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/)
|
||||
for extra context.
|
||||
4. Once you have reflected any feedback in the proposal draft,
|
||||
announce that the article is ready for submission (again, in the
|
||||
channel or in one of the weekly meetings): the assigned editor will
|
||||
|
|
@ -121,7 +124,7 @@ co-author](https://docs.github.com/en/pull-requests/committing-changes-to-your-p
|
|||
is done by adding `Co-authored-by: original-author-name
|
||||
<original-author@example.com>` to the commit message.
|
||||
|
||||
The number of PRs depends on where the article will be published:
|
||||
The number of PRs you open depends on where the article will be published:
|
||||
|
||||
1. If it's solely for the Contributor site: the PR should be opened in
|
||||
the
|
||||
|
|
@ -130,7 +133,7 @@ The number of PRs depends on where the article will be published:
|
|||
2. If it's to be mirrored in the main Kubernetes blog: after the
|
||||
previous step, a new PR is opened on
|
||||
[kubernetes/website](https://github.com/kubernetes/website),
|
||||
mentioning the original PR. The SIG-Docs Blog editorial team will,
|
||||
mentioning the original PR. Reviewers from SIG Docs Blog will,
|
||||
in this case, already been notified and involved in the initial PR.
|
||||
|
||||
|
||||
|
|
@ -186,7 +189,9 @@ Keep the following points in mind as you write in order to speed up the review p
|
|||
* As the author, never talk about your employer, sell, promote, or
|
||||
pitch; this is about upstream community endeavours and the
|
||||
individuals and groups that create it
|
||||
* Follow the [documentation style guide](https://kubernetes.io/docs/contribute/style/style-guide/).
|
||||
* Follow the [documentation style guide](https://kubernetes.io/docs/contribute/style/style-guide/);
|
||||
for blog articles these are informative guidelines rather than anything more strict, but
|
||||
it's still good to follow them where appropriate.
|
||||
|
||||
## Further Recommendations
|
||||
|
||||
|
|
|
|||
|
|
@ -13,3 +13,4 @@ These are all the spot lights that are published to date:
|
|||
| [Instrumentation](https://github.com/kubernetes/community/blob/master/sig-instrumentation/README.md) | [instrumentation](https://github.com/kubernetes/kubernetes/labels/sig%2Finstrumentation) | [Spotlight on SIG Instrumentation](https://kubernetes.io/blog/2023/02/03/sig-instrumentation-spotlight-2023/) | Imran Noor Mohamed | 2023-02-03 |
|
||||
| [Network](https://github.com/kubernetes/community/blob/master/sig-network/README.md) | [network](https://github.com/kubernetes/kubernetes/labels/sig%2Fnetwork) | [Spotlight on SIG Network](https://www.kubernetes.dev/blog/2023/05/09/sig-network-spotlight-2023/) | Sujay Dey | 2023-05-09 |
|
||||
| [CLI](https://github.com/kubernetes/community/blob/master/sig-cli/README.md) | [CLI](https://github.com/kubernetes/kubernetes/labels/sig%2Fcli) | [Spotlight on SIG CLI](https://www.kubernetes.dev/blog/2023/07/20/sig-cli-spotlight-2023/) | Arpit Agrawal | 2023-07-20 |
|
||||
| [Contributor Experience](https://github.com/kubernetes/community/blob/master/sig-contributor-experience/README.md) | [contributor-experience](https://github.com/kubernetes/kubernetes/labels/sig%2Fcontributor-experience) | [Spotlight on SIG Contributor Experience](https://kubernetes.io/blog/2023/08/14/sig-contribex-spotlight-2023/) | Fyka Ansari | 2023-08-14 |
|
||||
|
|
|
|||
|
|
@ -4,19 +4,20 @@
|
|||
|
||||
This handbook outlines expectations and responsibilities for Tech Leads as well as Contributor Comms team members who wish to contribute to technical efforts.
|
||||
|
||||
Tech leads' contributions further the Contributor Comms team's efforts to communicate contributors' stories by resolving technical issues and decisions around [contributor-site](https://www.kubernetes.dev/), social media automation tools [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets), and [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message).
|
||||
Tech leads' contributions further the Contributor Comms team's efforts to communicate contributors' stories by resolving technical issues and decisions around [contributor-site](https://www.kubernetes.dev/), social media automation tools [buffer](https://buffer.com/) and [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message).
|
||||
|
||||
[contributor-site](https://www.kubernetes.dev/) is a one-stop for Kubernetes contributor content and news. It brings important documentation scattered throughout the project into one central location.
|
||||
[Contributor-site](https://www.kubernetes.dev/) is a one-stop for Kubernetes contributor content and news. It brings important documentation scattered throughout the project into one central location.
|
||||
|
||||
Along with contributor-site there exist two automation tools that help:
|
||||
1. To create tweets (k8scontributors) via GitHub actions (see: [workflow](https://github.com/kubernetes-sigs/contributor-tweets/blob/main/.github/workflows/main.yml))
|
||||
2. To broadcasts messages across multiple slack channels (see: [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message))
|
||||
A shadow for the tech lead role is someone who is expected, and in training, to take over the lead role.
|
||||
|
||||
The [contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets) utilizes open source Github action [twitter-together](https://github.com/gr2m/twitter-together) project to automate tweet approval from an issue.
|
||||
Along with contributor-site these automation tools are being used:
|
||||
1. Slack-bot to broadcast messages across multiple slack channels (see: [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message))
|
||||
2. [buffer](https://buffer.com/) to create posts in social media platforms (X and mastodon)
|
||||
3. [Zapier](https://zapier.com/) to create and maintain automations (e.g posting zoom meeting to youtube)
|
||||
|
||||
## Minimum Skills and Requirements
|
||||
|
||||
- Are a member of the [Kubernetes GitHub Org]
|
||||
- Are a member of the Kubernetes GitHub Org
|
||||
- Good knowledge of Node.js, Hugo(docsy theme and frontmatter)
|
||||
- Have a basic experience in Go (for Slack bot)
|
||||
- Have a good understanding of Github actions
|
||||
|
|
@ -30,18 +31,25 @@ Team members: 2-3 hours per week.
|
|||
## General Expectations
|
||||
|
||||
- Be welcoming, be yourself
|
||||
- Take ownership of an issue and submit a PR for repositories like (especially if it's quick or relates to work you're already doing) Contributor-site, tweets, and, slack bot
|
||||
- Take ownership of an issue and submit a PR for repositories like (especially if it's quick or relates to work you're already doing) Contributor-site and, slack bot
|
||||
- Have an understanding of what an issue is about and able to triage them, or know who to contact to determine the required information
|
||||
- Coordinate work to fix any issues in automation tools to ensure valid tweet requests are fulfilled
|
||||
- Train new leads
|
||||
|
||||
Team members will be expected to keep an eye out for news or issues related to slack bot or Github automation. Common sources of such announcements are the k-dev mailing list and the #contributor-comms channel on Slack.
|
||||
Team members will be expected to keep an eye out for news or issues related to slack bot. Common sources of such announcements are the k-dev mailing list and the #contributor-comms channel on Slack.
|
||||
|
||||
## Associates Overview (Shadow)
|
||||
## Tech Lead Shadow Overview
|
||||
|
||||
Team members who wish to become technical leads shadow should express this desire to the current lead.
|
||||
Team members who wish to become tech leads should express this desire to the current lead(s). Leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan for them to take on responsibility including:
|
||||
|
||||
Leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan for them to take on responsibility including:
|
||||
* Being an active member of the Comms team, by following the activities and the regular meetings.
|
||||
* Demonstrated knowledge of the team's [README](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md) and [Charter](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/CHARTER.md).
|
||||
* Becoming a reviewer for relevant PRs.
|
||||
* Leading initiatives in the Contributor Comms subproject
|
||||
* Address and work with the team to fix techinical issues.
|
||||
* Familiar with tools like Buffer, zapier.
|
||||
|
||||
### Tech Lead Shadow Eligibility
|
||||
|
||||
* General familiarity with our repositories and automation tools
|
||||
* Willingness and ability to follow up with contributors about issues, on Github, Slack, and email, as appropriate
|
||||
|
|
|
|||
|
|
@ -4,18 +4,22 @@
|
|||
|
||||
This handbook outlines expectations and responsibilities for Social Media Leads as well as Contributor Comms team members who wish to contribute to social media efforts.
|
||||
|
||||
Social Media leads' contributions further the Contributor Comms team's efforts to communicate with contributors on a broad scale through social media. At the time of writing, the primary social media channel we communicate through is the [@K8sContributors handle on twitter](https://twitter.com/K8sContributors).
|
||||
Social Media leads' contributions further the Contributor Comms team's efforts to communicate with contributors on a broad scale through social media. At the time of writing, the primary social media channels we communicate through are the [@K8sContributors handle on X (twitter)](https://x.com/K8sContributors) and [@K8sContributors@hachyderm.io on Mastodon](https://hachyderm.io/@K8sContributors).
|
||||
|
||||
Any Kubernetes contributor can write tweets to be distributed through the twitter handle by utilizing the [kubernetes-sigs/contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets). This repo utilizes the open source [twitter-together](https://github.com/gr2m/twitter-together) project to automate tweeting approved from the @K8sContributor handle. The repo also features automation to convert issues into PRs, to make it easier to create tweets with minimal interaction with Github's PR process.
|
||||
The social media lead's role is to coordinate social media work across the Contributor Comms team. This includes maintaining the [Contributor Comms team social media guidelines]
|
||||
(https://github.com/kubernetes/community/blob/master/communication/contributor-comms/blogging-resources/social-guidelines.md) as the source of truth for social media process, etiquette, and ethics. As the social media landscape grows and changes, the social media lead should be ready to adapt by leading conversation and exploration around the new platform.
|
||||
|
||||
Do note that tweets targeting the greater Kubernetes community should potentially use the @Kubernetesio account. Tweets using this account must be coordinated with the CNCF. Ownership of @Kubernetesio does not reside within the Contributor Comms team. For any tweets to be coordinated with @Kubernetesio, you will need to make contact with CNCF marketing members in charge of the account. Tweets using the @kubernetesio account are often limited in the content and quantity that may be sent.
|
||||
Do note that important posts targeting the greater Kubernetes community (including end users) should potentially use the @Kubernetesio account. Posts using this account must be coordinated with the CNCF. Ownership of @Kubernetesio does not reside within the Contributor Comms team. For any posts to be coordinated with @Kubernetesio, you will need to make contact with CNCF marketing team members in charge of the account. Tweets using the @kubernetesio account are often limited in the content and quantity that may be sent.
|
||||
|
||||
A shadow for the social media lead role is someone who is expected, and in training, to take over the role.
|
||||
|
||||
## Minimum Skills and Requirements
|
||||
|
||||
- Are a member of the Kubernetes GitHub Org
|
||||
- Familiar with twitter by either having a personal account or managing another account (brand, oss project, employer, local nonprofit, etc)
|
||||
- Available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack
|
||||
- Familiar with the social media platforms the Contributor Comms team is actively using by either having a personal account or managing another account (brand, oss project, employer, local nonprofit, etc) on these platforms
|
||||
- Available to attend regular Contributor Comms meetings regularly
|
||||
- Able to collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack
|
||||
- Familiar with and able to maintain the [Contributor Comms team social media guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/blogging-resources/social-guidelines.md)
|
||||
|
||||
### Expected Time Investment
|
||||
|
||||
|
|
@ -24,23 +28,36 @@ Team members: 1-3 hours per week.
|
|||
|
||||
## General Expectations
|
||||
|
||||
- Rules for social posts and more can be found in [social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/social-guidelines.md)
|
||||
- Rules for social posts and more can be found in [social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/blogging-resources/social-guidelines.md)
|
||||
- Be welcoming, be yourself
|
||||
- Understanding, communicating, and setting/adjusting [social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/social-guidelines.md)
|
||||
- Coordinating work to create tweets, ensuring tweet requests are fulfilled
|
||||
- Working with other Contributor Comms leads, such as the Event Coordinator Lead, on social media tasks
|
||||
- Approving tweet PRs on [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets)
|
||||
- Understanding, communicating, and setting/adjusting the [Contributor Comms social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/blogging-resources/social-guidelines.md)
|
||||
- Coordinating work to create posts, ensuring social media post requests are fulfilled
|
||||
- Working with other Contributor Comms leads on social media tasks
|
||||
- Managing Buffer, including
|
||||
- communicating funding needs to the subproject lead (who will ensure they get communicated to the CNCF)
|
||||
- managing the team on Buffer, including adding and removing team members
|
||||
- Training new leads
|
||||
- Maintaining this document
|
||||
|
||||
The leader(s) of the social media team will be expected to monitor the @K8sContributors handle. Retweets, replies, and responding to replies appropriately fall under the purview of the social media lead. Time-sensitive tweets should also be handled directly by the team lead. Team leads should coordinate with team members to plan tweets in advance, particularly for large contributor-focused events such as KubeCon or Contributor Summit.
|
||||
The leader(s) of the social media team will be expected to monitor the @K8sContributors handle. Reposts, replies, and responding to replies appropriately fall under the purview of the social media lead. Time-sensitive posts should also be handled directly by the social media lead. Social Media leads should coordinate with team members to plan posts in advance, particularly for large contributor-focused events such as KubeCon or Contributor Summit.
|
||||
|
||||
Team members will be expected to keep an eye out for news in need of tweeting. Common sources of such announcements are the k-dev mailing list and the #sig-contribex-comms channel on Slack. Team members can submit less time-sensitive tweets to the [kubernetes-sigs/contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets) for review and tweeting.
|
||||
Team members will be expected to keep an eye out for news in need of posting. Common sources of such announcements are the k-dev mailing list and the #sig-contribex-comms channel on Slack. The Social Media Lead can add team members to Buffer so they can create posts for approval across social media platforms
|
||||
|
||||
## Associates Overview (Shadow)
|
||||
## Social Media Shadow Overview
|
||||
|
||||
### Overview and Eligibility
|
||||
Anyone that is interested in helping the social media team, and that finds the general expectations and requirements acceptable, can start working in the team and have their contributions to the project recognised. Additionally, some will feel that they want to make a step towards becoming Social Media Leads themselves.
|
||||
|
||||
- Becoming a shadow is something that should come as a result of existing involvement in the team, and not as a starting point; to be eligible to shadow for this role you will need to:
|
||||
- Be a regular member of the Comms team, by following the activities and the regular meetings.
|
||||
Have demonstrated knowledge of the social media processes and guidelines, namely by having been actively involved in the creation of social media posts.
|
||||
|
||||
Team members who want to become Social Media Leads _should express their desire to the current lead_; leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan to take on the necessary responsibility.
|
||||
|
||||
### Shadow Responsibilities
|
||||
|
||||
Team members who wish to become social media leads should express this desire to the current lead.
|
||||
Leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan for them to take on responsibility including:
|
||||
* Becoming an owner (approver privileges) on the [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets) repo
|
||||
* Watching for new tweet PRs and working with PR creators on scheduling/approving tweets
|
||||
* Watching for new tweet requests and ensuring they get assigned to team members or created directly
|
||||
* Taking on direct management of a social media account
|
||||
- Taking on approver privileges in Buffer
|
||||
- Watching for new social media requests and working with requestors on scheduling/approving posts
|
||||
- Ensuring new social media requests get completed either by assigned to team members or creating directly
|
||||
- Taking on direct management of social media accounts
|
||||
|
|
|
|||
|
|
@ -9,32 +9,33 @@ Contributor Comms Subproject Leads are general, top level leads of any and all m
|
|||
|
||||
General responsibilities which do not fall under an area lead may be assumed to be the responsibility of the Subproject Lead[s].
|
||||
|
||||
A shadow for the subproject lead role is someone who is expected, and in training, to take over the lead role.
|
||||
|
||||
## **Minimum Skills and Requirements**
|
||||
|
||||
A subproject lead should be:
|
||||
|
||||
|
||||
A subproject lead should be/have:
|
||||
|
||||
* A member of the [Kubernetes GitHub Org](https://github.com/kubernetes/org)
|
||||
* An active member of the Contributor Comms subproject
|
||||
* Experience leading initiatives in the Contributor Comms subproject
|
||||
* Demonstrated knowledge of the [team's charter](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/CHARTER.md).
|
||||
* Available to attend/lead regular Contributor Comms meetings and collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack
|
||||
* Able and willing to actively recruit members and shadows for the benefit of the entire team and the contributor
|
||||
* Able and willing to actively recruit members and shadows for the benefit of the entire team
|
||||
* Able and willing to ensure urgent/critical topics are communicated in a timely and appropriate fashion. This may involve writing communications directly and/or appropriately overseeing delegated work.
|
||||
* Strong communication skills. Setting and clarifying requirements, processes, and more.
|
||||
* Able and willing to regularly attend/contribute to SIG-level meetings and initiatives.
|
||||
* [Preferred] Familiar with managing a social media presence by either having personal accounts or managing another account (brand, OSS project, employer, local nonprofit, etc)
|
||||
|
||||
### **Expected Time Investment**
|
||||
|
||||
|
||||
Team leads: 3-5 hours per week. Shadows: 1-3 hours per week.
|
||||
|
||||
|
||||
## **General Expectations**
|
||||
|
||||
Contributor Communications Subproject Leads are responsible for a number of tasks that are delegated to the team from SIG Contributor Experience, this includes:
|
||||
|
||||
Subproject Lead-specific responsibilities include:
|
||||
|
||||
|
||||
|
||||
* Running Subproject Meetings
|
||||
* Uphold the Kubernetes Code of Conduct especially in terms of personal behavior and responsibility
|
||||
* Actively promote diversity and inclusion in the subproject
|
||||
|
|
@ -57,12 +58,23 @@ Subproject Lead-specific responsibilities include:
|
|||
|
||||
## **Subproject Lead Shadowing**
|
||||
|
||||
|
||||
Team members who wish to become subproject leads should express this desire to the current lead(s). Leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan for them to take on responsibility including:
|
||||
|
||||
|
||||
|
||||
* Regular meeting leadership
|
||||
* Gaining familiarity with key connections, such as the SIG-ContribEx Chairs
|
||||
* Becoming an owner (approver privileges) on relevant repos
|
||||
* Troubleshooting skills
|
||||
* Communication skills
|
||||
* Prioritization skills
|
||||
* Understanding and ownership of key subproject docs such as the [README](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md) and [Charter](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/CHARTER.md)
|
||||
|
||||
|
||||
### **Subproject Lead Shadow Eligibility**
|
||||
Becoming a shadow is something that should come as a result of existing involvement in the team, and not as a starting point; to be eligible to shadow for this role you will need to be/have:
|
||||
|
||||
* An active member of the Comms team, by following the activities and the regular meetings.
|
||||
* Demonstrated knowledge of the [team's charter](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/CHARTER.md).
|
||||
* An active contributor to the Contributor Comms subproject
|
||||
* Experience leading initiatives in the Contributor Comms subproject
|
||||
* Some experience working with Github and our PR process
|
||||
* Familiar with Buffer
|
||||
|
|
|
|||
|
|
@ -1,44 +0,0 @@
|
|||
# Comms Events Lead Role Handbook
|
||||
|
||||
**NOTE**: This role is deprecated as of mid 2023
|
||||
|
||||
## Overview
|
||||
|
||||
As Event Co-ordinator Lead, you are responsible for
|
||||
- connecting with organizers of contributor events such as the monthly community meeting or contributor summits
|
||||
- working with the Contributor Comms team to ensure communications about events are being created and promoted through various means including email (k-dev), slack (slack bot, etc), twitter (K8sContributors), etc.
|
||||
|
||||
Time Commitment:
|
||||
|
||||
1-3 hours a week from 0-1.5 months in
|
||||
2-5 hours a week from 1.5 months-to event
|
||||
|
||||
## Minimum skills and Requirements
|
||||
|
||||
- Kubernetes github org [membership](https://github.com/kubernetes/community/blob/master/community-membership.md)
|
||||
- familiarity with the workflow of [#sig-contributor-comms](https://github.com/kubernetes/community/tree/master/communication/contributor-comms)
|
||||
- has understanding of the [social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/social-guidelines.md)
|
||||
- Good grasp on general marketing activities surrounding events
|
||||
- Understanding of common forms of marketing communications
|
||||
- Event planning experience is a plus
|
||||
- Willing and able to directly coordinate across timezones and contributor groups
|
||||
- commitement for the role is relative and would vary depending upon events
|
||||
|
||||
## Expectations and tasjs
|
||||
|
||||
The core task for the role would be to stay current on [upcoming](https://www.kubernetes.dev/events/) events. Planning should be done with the team about the event, target audience, mode of communication, timeline, etc. This could be coordinated via a call or async conversatios. Sometimes, some big events might require you to join a weekly or bi-weekly call. The following are the possible tasks to perform (may vary depending upon the event).
|
||||
|
||||
- Creating a communication schedule - what, when, how, who
|
||||
- Promoting on different platforms like
|
||||
- emailing on [kdev](https://github.com/kubernetes/community/blob/master/communication/mailing-list-guidelines.md)
|
||||
- twitting from main or k8scontributor accounts
|
||||
- coordinating with CNCF(if required)
|
||||
- sending slack notification to various channels(depending on the target audience)
|
||||
- Assisting in the entire blog process
|
||||
- Coordinating with Contributor Comms team members to ensure above tasks are completed
|
||||
|
||||
Timeline for the communication can be crucial parameters so ideally timelines should at least begin to be decided weeks before the event.
|
||||
|
||||
## Shadowing the Event Coordinator Role
|
||||
|
||||
This role can include one or more shadows. The Event Coordinator Lead can delegate/assign tasks to the shadows. The expectation from a shadow is to work with the lead to develop a plan to adopt ownership of the role over time, including all tasks listed in the "Expectations and Tasks" section. The shadows to the Event Coordinator Lead are responsible for handling all Event Coordinator lead related activities in the absence of the Lead.
|
||||
|
|
@ -1,27 +1,56 @@
|
|||
# Blog Coordinator Handbook
|
||||
|
||||
This handbook outlines expectations and responsibilities for Blog coordinator as well as Contributor Comms team members who wish to contribute to blogging activities.
|
||||
This handbook outlines expectations and responsibilities for Blog
|
||||
coordinator as well as Contributor Comms team members who wish to
|
||||
contribute to blogging activities.
|
||||
|
||||
Writing and sharing articles is one of the ways through which Kubernetes contributors add to the community, and the Blog Coordinator role exists to
|
||||
Writing and sharing articles is one of the ways through which
|
||||
Kubernetes contributors add to the community, and the Blog Coordinator
|
||||
role exists to
|
||||
|
||||
1. Serve as an initial point of contact for content suggestions
|
||||
2. Help contributors to navigate the existing publishing processes
|
||||
3. Assist in determining the final publishing targets of the content.
|
||||
4. Coordinate with SIG-Docs in the publishing process, namely by following and improving the Blogging Guidelines.
|
||||
5. Coordinate with the rest of the Contributor Comms team, and specifically the Social Media Coordinator, in the best ways to broaden external awareness of published content.
|
||||
4. Coordinate with SIG-Docs in the publishing process, namely by
|
||||
following and improving the Blogging Guidelines.
|
||||
5. Coordinate with the rest of the Contributor Comms team, and
|
||||
specifically the Social Media Coordinator, in the best ways to
|
||||
broaden external awareness of published content.
|
||||
|
||||
The [Kubernetes Contributor Blog](https://www.kubernetes.dev/blog/) is one of the most direct points of entry for those that want to share with a wider audience. The role of the Blog Coordinator is to guide those that want to contribute in the best way to do so, while coordinating with the rest of the team (including other Contributor Comms team members) to assign editors, reviewers and other roles to new submissions.
|
||||
The [Kubernetes Contributor Blog](https://www.kubernetes.dev/blog/) is
|
||||
one of the most direct points of entry for those that want to share
|
||||
with a wider audience. The role of the Blog Coordinator is to guide
|
||||
those that want to contribute in the best way to do so, while
|
||||
coordinating with the rest of the team (including other Contributor
|
||||
Comms team members) to assign editors, reviewers and other roles to
|
||||
new submissions.
|
||||
|
||||
The Blog Coordinator has an active involvement in defining, with others, the [Blogging Guidelines](https://hackmd.io/@fsm/blog-guidelines), and should constantly seek to improve them, with an eye on the improvement of the contributor experience.
|
||||
The Blog Coordinator has an active involvement in defining, with
|
||||
others, the [Blogging
|
||||
Guidelines](https://hackmd.io/@fsm/blog-guidelines), and should
|
||||
constantly seek to improve them, with an eye on the improvement of the
|
||||
contributor experience.
|
||||
|
||||
|
||||
### Minimum Skills and Requirements
|
||||
|
||||
Those in this role should ideally:
|
||||
|
||||
* Be a member of the [Kubernetes GitHub Org](https://github.com/kubernetes/)
|
||||
* Have some familiarity with blogging platforms and editing tools; specific knowledge of Markdown, GitHub and Hugo is a plus.
|
||||
* Be available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack
|
||||
* Be a member of the [Kubernetes GitHub
|
||||
Org](https://github.com/kubernetes/)
|
||||
* Have some familiarity with blogging platforms and editing tools;
|
||||
specific knowledge of Markdown and Hugo is a plus.
|
||||
* Have some familiarity with Git and GitHub-based workflows; these are
|
||||
extensively used in the Kubernetes project, and specifically in both
|
||||
the contributor site and the main website.
|
||||
* Be available to either attend regular Contributor Comms meetings or
|
||||
collaborate asynchronously via the #sig-contribex-comms channel in
|
||||
the Kubernetes Slack.
|
||||
* Have reasonable working knowledge of English, particularly in the
|
||||
written form.
|
||||
* Have an interest in interacting with others; blogging is almost
|
||||
always a group effort that involves working with authors to achieve
|
||||
a commonly agreed result.
|
||||
|
||||
#### Expected time commitment
|
||||
|
||||
|
|
@ -31,18 +60,69 @@ Those in this role should ideally:
|
|||
### General Expectations
|
||||
|
||||
1. Be ready to help those wanting to contribute to the blogs.
|
||||
2. Understand the Blogging Guidelines and assist contributors in following them.
|
||||
3. Help in determining applicability of the proposed content, with the rest of the team: this includes discussion in the Slack channel or regular meeting.
|
||||
2. Understand the Blogging Guidelines and assist contributors in
|
||||
following them.
|
||||
3. Help in determining applicability of the proposed content, with the
|
||||
rest of the team: this includes discussion in the Slack channel or
|
||||
regular meeting.
|
||||
4. Identify team members that can review blog submissions.
|
||||
5. Discuss with SIG-Docs, when needed, for possible publication in the main Kubernetes site.
|
||||
5. Discuss with SIG-Docs, when needed, for possible publication in the
|
||||
main Kubernetes site.
|
||||
6. Review blog submissions.
|
||||
7. Open the blog submission PR (with the author as Co-author), or find someone that can assist in this tasks within the Contributor Comms team.
|
||||
7. Open the blog submission PR (with the author as Co-author), or find
|
||||
someone that can assist in this tasks within the Contributor Comms
|
||||
team.
|
||||
8. Follow up submitted PRs and help with the approval process.
|
||||
|
||||
### Associates Overview (Shadow)
|
||||
|
||||
Team members who which to become Blogging Leads should express their desire to the current lead; leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan to take on responsibility, including:
|
||||
#### Description and eligibility
|
||||
|
||||
* Become a reviewer of new submitted content.
|
||||
* Open the PRs and follow them through.
|
||||
* Provide assistance to new contributors that are asking how to submit content.
|
||||
Anyone that is interested in helping the blogging team, and that
|
||||
finds the general expectations and requirements acceptable, can start
|
||||
working in the team and have their contributions to the project
|
||||
recognised. Additionally, some will feel that they want to make a step
|
||||
towards becoming Blogging Leads themselves.
|
||||
|
||||
Becoming a shadow is something that should come as a result of
|
||||
existing involvement in the team, and not as a starting point; to be
|
||||
eligible to shadow for this role you will need to:
|
||||
|
||||
* Be a regular member of the Comms team, by following the
|
||||
activities and the regular meetings.
|
||||
* Have demonstrated knowledge of the blogging process and guidelines,
|
||||
namely by having been actively involved in the publishing process of
|
||||
articles.
|
||||
|
||||
Team members who want to become Blogging Leads _should express their
|
||||
desire to the current lead_; leads should work with shadows to
|
||||
understand their capacity to take on the needs of the lead role and
|
||||
work with the shadow on a plan to take on the necessary
|
||||
responsibility.
|
||||
|
||||
#### Expected contributions
|
||||
|
||||
Some of the identified requirements for blogging shadows are:
|
||||
|
||||
* **Become a reviewer of new submitted content**, by leading communication
|
||||
with content creators and guiding them through the publishing
|
||||
process.
|
||||
* **Open the PRs and follow them through**, helping content creators
|
||||
in the more processual aspects of publishing, keeping them informed
|
||||
of the necessary steps and following the process untul completion.
|
||||
* **Provide assistance to new contributors that are asking how to
|
||||
submit content**, by monitoring the Slack channel, Github, and other
|
||||
sources.
|
||||
* **Make status updates in the SIG Contribex Comms meetings**, keeping
|
||||
the status of the relevant projects up-to-date (e.g., in the project
|
||||
board) and having a broad understanding of the different ongoing tasks.
|
||||
|
||||
This requirements are aligned with the general expectations described
|
||||
above, but in the context of shadowing they follow a more structured
|
||||
approach. The acting Blogging Lead will discuss the steps that need to
|
||||
be taken to make the shadowing programme helpful and achieve the desired result.
|
||||
|
||||
Changes in roles are done by the SIG Contribex Comms subproject team
|
||||
based on different inputs and needs, but having shadows that are ready
|
||||
to assume a leading position is an important part of what makes it
|
||||
possible.
|
||||
|
|
|
|||
|
|
@ -1,84 +0,0 @@
|
|||
# Storytellers 📖 Handbook
|
||||
|
||||
## Overview
|
||||
|
||||
Contributor Comms depends on great storytelling to get the message out about our amazing community.
|
||||
|
||||
It's no secret that governance and technical documentation can be kind of on the boring side. And that's ok–it's not always there for entertainment purposes. It is about providing valuable information and getting you where you need to go. But that said, an important message can be lost without an entertaining messenger.
|
||||
|
||||
In this role, Storytellers are here to help Kubernetes contributors hear the latest news in the most entertianing ways. Storytellers will take us on journeys through words and visuals to help us craft.
|
||||
|
||||
## Workflow ⚡️
|
||||
|
||||
Storytelling is welcome in any medium that can be supported by the Contributor Comms team. This includes but is not limited to written word–as outlined in [blogging guidelines]–or through video following our [YouTube guidelines].
|
||||
|
||||
Storytellers are constantly building new ways to share, and these resources are gathered in the [storytelling resources folder].
|
||||
|
||||
### Contributor Comms Process
|
||||
|
||||
#### Idea Paths
|
||||
|
||||
There are multiple ways to successfully contribute a Kubernetes blog post. Here are some of the common paths to help you do so:
|
||||
|
||||
**To start:**
|
||||
|
||||
* Open a [Contributor Comms Requests issue](https://github.com/kubernetes/community/issues) to share your blog idea, or attend an [Contributor Comms team](https://github.com/kubernetes/community/tree/master/communication/contributor-comms) meeting to discuss it ahead of time
|
||||
|
||||
**To write:**
|
||||
|
||||
* Create an initial draft -- it is always easier to work from some written down ideas than to do so from scratch
|
||||
* A draft can be written in:
|
||||
* Google Docs or
|
||||
* Markdown (and shared via [Gist](https://gist.github.com/) or [HackMD](https://hackmd.io/))
|
||||
* Connect with a storyteller -- if you reach out to Contributor Comms, you will be paired with someone to help you through writing, editing, and getting your article published
|
||||
* Discussion happens via GitHub issue or through working group meetings
|
||||
* This includes working with Contributor Comms team to polish, and format your blog post
|
||||
* There is not a single canonical format for documents, but we do have [guidelines for effective articles](https://github.com/kubernetes/community/tree/master/sig-docs/blog-subproject#blog-guidelines)
|
||||
* There are further technical considerations by the [Blog team](https://github.com/kubernetes/community/blob/4026287dc3a2d16762353b62ca2fe4b80682960a/sig-docs/blog-subproject/README.md#submit-a-post)
|
||||
|
||||
When it's ready, submit the blog post:
|
||||
|
||||
* Go to the `kubernetes/website` repository
|
||||
* Open a PR with your added blog post
|
||||
* If you need help with this process, Contributor Comms will look to pair you with someone for PR and shepherd it through the review cycle
|
||||
|
||||
Or if you already have everything you think you need you can:
|
||||
|
||||
* Go to the `kubernetes/website` repo and send a PR
|
||||
* There's a Kubernetes blog team that will walk you through [the process](https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/)
|
||||
|
||||
### Tips
|
||||
|
||||
Converting a Google Doc to markdown? Here is a helpful way to do so:
|
||||
|
||||
* go to: https://discuss.kubernetes.io/
|
||||
* Open a new topic
|
||||
* Paste the Google Doc into new topic window
|
||||
* Discourse will automatically convert it to markdown 🎉
|
||||
* Now you can copy the markdown text, with all its original formatting, and paste it into your blog post file (this will often be a text file you are editing on your computer from a text editor like VS Code)
|
||||
* Be sure to add the syntax required at the top of the blog post (see links above)
|
||||
* Now you are ready to submit it as a PR
|
||||
|
||||
## Minimum Skills and Requirements
|
||||
|
||||
- Have a passion for telling stories, technical writing, journalism, and painting pictures with words
|
||||
- Desire to be a Kubernetes Org Member and if not already, work your way towards membership
|
||||
- Helpful but not required: Comfortable with working with GitHub workflows or working in a collaborative document like Hackmd.io
|
||||
|
||||
## Expectations
|
||||
|
||||
Anyone is welcome to contribute when they have time. The core expectation of storytelling is taking responsibility for getting the story from inception to published.
|
||||
|
||||
If you would like to be listed as a member of the team, here are the expectations:
|
||||
|
||||
1. Be prepared to write one blog a quarter and participate in edits to other articles. The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue.
|
||||
2. Storytellers are expected to attend at least one Contributor Comms meeting a month or check-in to remain active.
|
||||
3. Remain non-partial: if you receive a request to write about a project, an individual, or a group of people from your employer, you should ask an impartial blogger to write it.
|
||||
4. As with all contribution to Kubernetes, adhere to the [code of conduct](/code-of-conduct.md), values, and principles of the project.
|
||||
|
||||
There are no shadow roles for Storytellers. If Storytellers are interested in becoming a shadow they can read more about the available leadership roles in the Contributor Comms [Role handbooks](https://github.com/kubernetes/community/tree/master/communication/contributor-comms/role-handbooks).
|
||||
|
||||
[blogging guidelines]: ../storytelling-resources/blog-guidelines.md
|
||||
[YouTube guidelines]: /communication/youtube/youtube-guidelines.md
|
||||
[storytelling resources folder]: ../storytelling-resources/
|
||||
[Marketing Council Handbook]: ../role-handbooks/council.md
|
||||
|
|
@ -5,9 +5,11 @@ channels:
|
|||
- name: africa-dev
|
||||
- name: airflow-operator
|
||||
- name: akri
|
||||
- name: aks-engine-users
|
||||
- name: azure-aks
|
||||
id: CU3N85WJK
|
||||
- name: aks-engine-dev
|
||||
id: CU1CXUHN0
|
||||
archived: true
|
||||
- name: announcements
|
||||
- name: antrea
|
||||
- name: api-priority-and-fairness
|
||||
|
|
@ -49,6 +51,7 @@ channels:
|
|||
- name: cka-exam-prep
|
||||
- name: ckad-exam-prep
|
||||
- name: cks-exam-prep
|
||||
- name: claudie
|
||||
- name: client-go-docs
|
||||
archived: true
|
||||
- name: cluster-addons
|
||||
|
|
@ -95,6 +98,7 @@ channels:
|
|||
- name: de-events
|
||||
- name: de-users
|
||||
- name: deppy-dev
|
||||
archived: true
|
||||
- name: devfile
|
||||
- name: devspace
|
||||
- name: devstats
|
||||
|
|
@ -107,6 +111,7 @@ channels:
|
|||
- name: draft-users
|
||||
- name: druid-operator
|
||||
- name: ebpf
|
||||
- name: educates
|
||||
- name: eks
|
||||
- name: eksctl
|
||||
- name: elastickube
|
||||
|
|
@ -116,7 +121,6 @@ channels:
|
|||
- name: emea-users
|
||||
- name: eraser
|
||||
- name: es-users
|
||||
- name: etcd
|
||||
- name: etcdadm
|
||||
- name: evented-pleg
|
||||
- name: events
|
||||
|
|
@ -226,6 +230,7 @@ channels:
|
|||
- name: kots
|
||||
id: CFFKXV0JZ
|
||||
- name: kpack
|
||||
archived: true
|
||||
- name: kpt
|
||||
- name: kr-dev
|
||||
- name: kr-users
|
||||
|
|
@ -272,15 +277,19 @@ channels:
|
|||
archived: true
|
||||
- name: kubernetes-careers
|
||||
- name: kubernetes-client
|
||||
- name: kubernetes-contributors
|
||||
- name: kubernetes-new-contributors
|
||||
id: C09R23FHP
|
||||
# kubernetes-docs-* channels are defined in sig-docs/
|
||||
- name: kubernetes-novice
|
||||
- name: kubernetes-operators
|
||||
- name: kubernetes-org-members
|
||||
- name: kubernetes-ruby
|
||||
archived: true
|
||||
- name: kubernetes-security
|
||||
- name: kubernetes-streaming
|
||||
archived: true
|
||||
- name: kubernetes-teachers
|
||||
archived: true
|
||||
- name: kubernetes-users
|
||||
- name: kubeslice
|
||||
- name: kubespray
|
||||
|
|
@ -302,6 +311,8 @@ channels:
|
|||
- name: litmus
|
||||
- name: litmus-dev
|
||||
- name: lokomotive
|
||||
archived: true
|
||||
- name: magnum-cluster-api
|
||||
- name: malaysia-users
|
||||
- name: malta-users
|
||||
- name: meet-our-contributors
|
||||
|
|
@ -363,6 +374,7 @@ channels:
|
|||
- name: okteto
|
||||
- name: olm-dev
|
||||
- name: open-cluster-mgmt
|
||||
- name: open-component-model
|
||||
- name: opencontainers
|
||||
- name: openebs
|
||||
- name: openebs-dev
|
||||
|
|
@ -372,6 +384,7 @@ channels:
|
|||
- name: openshift-users
|
||||
- name: openstack-helm
|
||||
- name: openstack-kolla
|
||||
- name: openstack-magnum
|
||||
- name: operator-builder
|
||||
- name: operator-framework-community
|
||||
- name: operator-sdk-dev
|
||||
|
|
@ -402,9 +415,11 @@ channels:
|
|||
- name: rktnetes
|
||||
- name: ro-users
|
||||
- name: rukpak-dev
|
||||
archived: true
|
||||
- name: ru-users
|
||||
- name: scaleway-k8s
|
||||
- name: schemahero
|
||||
- name: sovereign-cloud-stack
|
||||
- name: se-users
|
||||
- name: sealed-secrets
|
||||
- name: security-profiles-operator
|
||||
|
|
@ -435,11 +450,14 @@ channels:
|
|||
archived: true
|
||||
- name: sig-contribex
|
||||
- name: sig-contribex-meetings
|
||||
archived: true
|
||||
- name: sig-contribex-comms
|
||||
- name: sig-contribex-elections
|
||||
- name: sig-contribex-triage
|
||||
archived: true
|
||||
# sig-docs* channels are defined in sig-docs/
|
||||
- name: sig-etcd
|
||||
id: C3HD8ARJ5
|
||||
- name: sig-high-availability
|
||||
archived: true
|
||||
- name: sig-instrumentation
|
||||
|
|
@ -538,3 +556,4 @@ channels:
|
|||
- name: yaml-overlay-tool
|
||||
- name: zarf
|
||||
- name: zarf-dev
|
||||
- name: krkn
|
||||
|
|
|
|||
|
|
@ -11,7 +11,9 @@ usergroups:
|
|||
# Sorted alphabetically!
|
||||
- bart0sh
|
||||
- byako
|
||||
- catblade
|
||||
- elezar
|
||||
- klihub
|
||||
- klueska # subproject owner
|
||||
- obiTrinobiIntel
|
||||
- pohly # subproject owner
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ usergroups:
|
|||
# - Emeritus Adviser
|
||||
# - SIG Release leads
|
||||
#
|
||||
# Current release cycle: https://git.k8s.io/sig-release/releases/release-1.24/release-team.md
|
||||
# Current release cycle: https://git.k8s.io/sig-release/releases/release-1.29/release-team.md
|
||||
- name: release-team-leads
|
||||
long_name: Release Team Leads
|
||||
description: >-
|
||||
|
|
@ -49,15 +49,15 @@ usergroups:
|
|||
- sig-release
|
||||
members:
|
||||
- cpanato # SIG Release Technical Lead
|
||||
- gracenng # 1.28 RT Lead
|
||||
- helayoty # 1.28 RT Lead Shadow
|
||||
- jeremyrickard # SIG Release Chair
|
||||
- justaugustus # SIG Release Chair
|
||||
- leonardpahlke # 1.28 Emeritus Adviser
|
||||
- marosset # 1.28 RT Lead Shadow
|
||||
- mickeyboxell # 1.28 RT Lead Shadow
|
||||
- neoaggelos # 1.28 RT Lead Shadow
|
||||
- mehabhalodiya # 1.29 RT Lead Shadow
|
||||
- mickeyboxell # 1.29 RT Lead Shadow
|
||||
- neoaggelos # 1.29 RT Lead Shadow
|
||||
- Priyankasaggu11929 # 1.29 RT Lead
|
||||
- puerco # SIG Release Technical Lead
|
||||
- ramrodo # 1.29 RT Lead Shadow
|
||||
- salaxander # 1.29 Emeritus Adviser
|
||||
- saschagrunert # SIG Release Chair
|
||||
- Verolop # SIG Release Technical Lead
|
||||
|
||||
|
|
|
|||
|
|
@ -195,12 +195,12 @@ usergroups:
|
|||
- steering-committee
|
||||
members:
|
||||
- bentheelder
|
||||
- cblecker
|
||||
- cpanato
|
||||
- justaugustus
|
||||
- mrbobbytables
|
||||
- pacoxu
|
||||
- palnabarun
|
||||
- tpepper
|
||||
- pohly
|
||||
- soltysh
|
||||
|
||||
- name: grafana-operator-maintainers
|
||||
long_name: Grafana Operator Maintainers
|
||||
|
|
@ -232,13 +232,15 @@ usergroups:
|
|||
- devfile
|
||||
members:
|
||||
- elsony
|
||||
- feloy
|
||||
- jasperchui
|
||||
- johnmcollier
|
||||
- kim-tsao
|
||||
- maysunfaisal
|
||||
- michael-valdron
|
||||
- mike-hoang
|
||||
- rm3l
|
||||
- rtaniwa
|
||||
- schultzp2020
|
||||
- thepetk
|
||||
- yangcao77
|
||||
|
||||
- name: cluster-api-release-team
|
||||
|
|
@ -283,12 +285,12 @@ usergroups:
|
|||
long_name: Kubernetes GitHub Admins
|
||||
description: Administrators of the Kubernetes GitHub organisations
|
||||
members:
|
||||
- ameukam
|
||||
- cblecker
|
||||
- idvoretskyi
|
||||
- MadhavJivrajani
|
||||
- mrbobbytables
|
||||
- nikhita
|
||||
- palnabarun
|
||||
- Priyankasaggu11929
|
||||
|
||||
- name: kubestellar-devs
|
||||
long_name: KubeStellar Development Team
|
||||
|
|
|
|||
|
|
@ -33,6 +33,7 @@ users:
|
|||
calebamiles: U1ZDD4CUR
|
||||
camilamacedo86: UJDM393EH
|
||||
castrojo: U1W1Q6PRQ
|
||||
catblade: URCV5RDSB
|
||||
cblecker: U3EDWR9FV
|
||||
cdrage: U2TU9NPH9
|
||||
CecileRobertMichon: U98JPHB2M
|
||||
|
|
@ -93,6 +94,7 @@ users:
|
|||
jakexks: U0AKBM9EC
|
||||
JamesLaverack: U9MK7274Y
|
||||
Jason: UB272379N
|
||||
jasperchui: U01DRL00ES3
|
||||
jberkhahn: U7Q21LH2S
|
||||
jdumars: U0YJS6LHL
|
||||
jeefy: U5MCFK468
|
||||
|
|
@ -131,6 +133,7 @@ users:
|
|||
liggitt: U0BGPQ6DS
|
||||
listx: UFCU8S8P3
|
||||
lukehinds: UN2P2M4F4
|
||||
MadhavJivrajani: U01L7R0JGCE
|
||||
maelvls: UKYB4CKNJ
|
||||
marc-obrien: UL51BRL9Y
|
||||
margocrawf: U01FWP2K74J
|
||||
|
|
@ -140,12 +143,12 @@ users:
|
|||
mattmoyer: U0DRP8H42
|
||||
maysunfaisal: U01DEHK2YUB
|
||||
mbbroberg: U18JTHMDY
|
||||
mehabhalodiya: U024HPAQDC1
|
||||
micahhausler: U1WJ1BZA5
|
||||
michael-valdron: U03LXKVS0SX
|
||||
mickeyboxell: UH0K0EC6S
|
||||
microwavables: UAF606ESE
|
||||
mik-dass: UCUULSG1W
|
||||
mike-hoang: U03PDV4LS1Z
|
||||
ming-qiu: U02JVSL5550
|
||||
mjlshen: UN08SUPPD
|
||||
mkorbi: UEBLUUA0P
|
||||
|
|
@ -163,10 +166,12 @@ users:
|
|||
nprokopic: UR434B8TS
|
||||
nrb: U7S597E00
|
||||
nzoueidi: UBU72MWP2
|
||||
obiTrinobiIntel: U02UNAXF74H
|
||||
onlydole: U1DD4AZND
|
||||
oscr: U0183J37JUQ
|
||||
p0lyn0mial: U1Q8CER5M
|
||||
pabloschuhmacher: U01AAGZ06KU
|
||||
pacoxu: UNVHE8R8A
|
||||
palnabarun: UBH9NTMBM
|
||||
paolo: U01CGS609EY
|
||||
paris: U5SB22BBQ
|
||||
|
|
@ -177,12 +182,13 @@ users:
|
|||
pohly: U91901TMF
|
||||
prajyot-parab: U02MVRCN8CX
|
||||
prietyc123: U01D4MBLM52
|
||||
psaggu: U012EE74CU8
|
||||
Priyankasaggu11929: U012EE74CU8
|
||||
puerco: ULGHLJ7TP
|
||||
PurneswarPrasad: U027CFKVAB0
|
||||
pweil-: U0AL6882X
|
||||
r-lawton: U019CNHR2E6
|
||||
rajula96reddy: U7K9EK1HC
|
||||
ramrodo: UU74ZC2RX
|
||||
rashmigottipati: U013T1DD3PW
|
||||
razashahid107: U05FB1L2YM8
|
||||
reylejano: U01GDNJL5MW
|
||||
|
|
@ -194,6 +200,7 @@ users:
|
|||
rtaniwa: U03K27HLHKN
|
||||
s-urbaniak: U0DT660QM
|
||||
sadysnaat: UNQPKAQHE
|
||||
salaxander: UDHV1RXB2
|
||||
sammy: U8NJFL023
|
||||
sandipanpanda: U02A47HJ517
|
||||
SaranBalaji90: U6PNPSULW
|
||||
|
|
@ -201,7 +208,6 @@ users:
|
|||
savitharaghunathan: UC8U2V3BM
|
||||
sayantani11: U028S6XNVSN
|
||||
sbueringer: U48TE1L75
|
||||
schultzp2020: U030K8UQA2G
|
||||
scott-seago: UHGD79E78
|
||||
sethmccombs: U92LLUZ8A
|
||||
sgtcodfish: U01PQ8N3PM1
|
||||
|
|
@ -209,6 +215,7 @@ users:
|
|||
shubham-pampattiwar: U01QW84HBBN
|
||||
simplytunde: UAY1NBYHE
|
||||
Sladyn Nunes: UQ9J177Q8
|
||||
soltysh: U0B4CS1GF
|
||||
stevekuznetsov: U0DUKNE6B
|
||||
sttts: U0A2VFE8J
|
||||
Sujay Pillai: UBW3N1VGW
|
||||
|
|
@ -221,6 +228,7 @@ users:
|
|||
tejal29: UACD7R316
|
||||
theishshah: U01891A4TRS
|
||||
thejoycekung: U01AY4VHX25
|
||||
thepetk: U04NW4PPY8N
|
||||
tobiasgiese: U01C1NM8D8F
|
||||
tpepper: U6UB5V4TX
|
||||
tstromberg: UCSL5SJ8Z
|
||||
|
|
|
|||
|
|
@ -183,50 +183,17 @@ in an [OWNERS] file (for repos using the bot).
|
|||
- Mentor contributors and reviewers
|
||||
- May approve code contributions for acceptance
|
||||
|
||||
## Subproject Owner
|
||||
|
||||
**Note:** This is a generalized high-level description of the role, and the
|
||||
specifics of the subproject owner role's responsibilities and related
|
||||
processes *MUST* be defined for individual SIGs or subprojects.
|
||||
|
||||
Subproject Owners are the technical authority for a subproject in the Kubernetes
|
||||
project. They *MUST* have demonstrated both good judgement and responsibility
|
||||
towards the health of that subproject. Subproject Owners *MUST* set technical
|
||||
direction and make or approve design decisions for their subproject - either
|
||||
directly or through delegation of these responsibilities.
|
||||
## Subproject Lead
|
||||
|
||||
**Defined by:** *owners* entry in subproject [OWNERS] files as defined by [sigs.yaml] *subproject.owners*
|
||||
|
||||
### Requirements
|
||||
The [SIG Governance][sig-governance-subproject-lead] mentions in details the responsibilities of a Subproject Lead.
|
||||
|
||||
The process for becoming an subproject Owner should be defined in the SIG
|
||||
charter of the SIG owning the subproject. Unlike the roles outlined above, the
|
||||
Owners of a subproject are typically limited to a relatively small group of
|
||||
decision makers and updated as fits the needs of the subproject.
|
||||
## Subproject Owner
|
||||
|
||||
The following apply to the subproject for which one would be an owner.
|
||||
**Defined by:** *owners* entry in subproject [OWNERS] files as defined by [sigs.yaml] *subproject.owners*
|
||||
|
||||
- Deep understanding of the technical goals and direction of the subproject
|
||||
- Deep understanding of the technical domain of the subproject
|
||||
- Sustained contributions to design and direction by doing all of:
|
||||
- Authoring and reviewing proposals
|
||||
- Initiating, contributing and resolving discussions (emails, GitHub issues, meetings)
|
||||
- Identifying subtle or complex issues in designs and implementation PRs
|
||||
- Directly contributed to the subproject through implementation and / or review
|
||||
|
||||
### Responsibilities and privileges
|
||||
|
||||
The following apply to the subproject for which one would be an owner.
|
||||
|
||||
- Make and approve technical design decisions for the subproject.
|
||||
- Set technical direction and priorities for the subproject.
|
||||
- Define milestones and releases.
|
||||
- Mentor and guide approvers, reviewers, and contributors to the subproject.
|
||||
- Ensure continued health of subproject
|
||||
- Adequate test coverage to confidently release
|
||||
- Tests are passing reliably (i.e. not flaky) and are fixed when they fail
|
||||
- Ensure a healthy process for discussion and decision making is in place.
|
||||
- Work with other subproject owners to maintain the project's overall health and success holistically
|
||||
The [SIG Governance][sig-governance-subproject-owner] mentions in details the responsibilities of a Subproject Owner.
|
||||
|
||||
## Inactive members
|
||||
|
||||
|
|
@ -281,3 +248,5 @@ before being able to contribute effectively.
|
|||
[elevated set of permissions]: #Responsibilities-and-privileges
|
||||
[Devstats project]: https://k8s.devstats.cncf.io/
|
||||
[continuously active]: #inactive-members
|
||||
[sig-governance-subproject-lead]: /committee-steering/governance/sig-governance.md#subproject-lead
|
||||
[sig-governance-subproject-owner]: /committee-steering/governance/sig-governance.md#subproject-owner
|
||||
|
|
|
|||
|
|
@ -425,6 +425,11 @@ Conditions are most useful when they follow some consistent conventions:
|
|||
Conditions should follow the standard schema included in [k8s.io/apimachinery/pkg/apis/meta/v1/types.go](https://github.com/kubernetes/apimachinery/blob/release-1.23/pkg/apis/meta/v1/types.go#L1432-L1492).
|
||||
It should be included as a top level element in status, similar to
|
||||
```go
|
||||
// +listType=map
|
||||
// +listMapKey=type
|
||||
// +patchStrategy=merge
|
||||
// +patchMergeKey=type
|
||||
// +optional
|
||||
Conditions []metav1.Condition `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"`
|
||||
```
|
||||
|
||||
|
|
@ -979,7 +984,7 @@ All forms of defaulting should only make the following types of modifications:
|
|||
- Setting previously unset fields
|
||||
- Adding keys to maps
|
||||
- Adding values to arrays which have mergeable semantics
|
||||
(`patchStrategy:"merge"` attribute in the type definition)
|
||||
(`+listType=map` tag or `patchStrategy:"merge"` attribute in the type definition)
|
||||
|
||||
In particular we never want to change or override a value that was provided by
|
||||
the user. If they requested something invalid, they should get an error.
|
||||
|
|
@ -1471,8 +1476,8 @@ due to invalid data provided as part of the request.
|
|||
|
||||
|
||||
* `429 StatusTooManyRequests`
|
||||
* Indicates that the either the client rate limit has been exceeded or the
|
||||
server has received more requests then it can process.
|
||||
* Indicates that either the client rate limit has been exceeded or the
|
||||
server has received more requests than it can process.
|
||||
* Suggested client recovery behavior:
|
||||
* Read the `Retry-After` HTTP header from the response, and wait at least
|
||||
that long before retrying.
|
||||
|
|
|
|||
|
|
@ -6,13 +6,13 @@ Feature gates are intended to cover the development life cycle of a feature - th
|
|||
|
||||
## Lifecycle
|
||||
|
||||
Feature progress through `Alpha` -> `Beta` -> `GA`. Sometimes we end up deciding that a feature is not going to be supported and we end up marking them as `Deprecated`.
|
||||
Features generally progress through `Alpha` -> `Beta` -> `GA`. Sometimes we end up deciding that a feature is not going to be supported and we end up marking them as `Deprecated`.
|
||||
|
||||
The majority of features will go through all three stages, but occasionally there are features which may skip stages.
|
||||
|
||||
When we add a feature flag, we basically add if/else conditions to ensure that a feature is ONLY activated when either the default is on or if the deployer has switched it on explicitly. When a feature gate is disabled, the system should behave as if the feature doesn't exist. The only exception to this is [API input validation](https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecating-parts-of-the-api) on updates, which should preserve and validate data if and only if it was present before the update (which could occur in case of a version rollback).
|
||||
|
||||
There is no supported way to trigger a feature gate at runtime for production Kubernetes use. A feature gate is typically toggled by a component restart.
|
||||
There is no supported way to change a feature gate at runtime for production Kubernetes use. A feature gate is typically toggled by a component restart.
|
||||
|
||||
Unless an exception is granted for a particular feature, as documented and approved as part of [Production Readiness Review], it is expected that:
|
||||
|
||||
|
|
@ -39,7 +39,7 @@ Unless an exception is granted for a particular feature, as documented and appro
|
|||
* `Default` is always set to `false`
|
||||
* `LockToDefault` is not set. Defaults to `false`
|
||||
|
||||
By default it is not switched on. This enables folks to switch on the feature using the command line. All API changes must start with an Alpha gate, which makes it possible to rollback from future versions.
|
||||
By default Alpha features are not switched on. This enables folks to switch on the feature using the command line. All API changes must start with an Alpha gate, which makes it possible to rollback from future versions.
|
||||
|
||||
## Beta Features
|
||||
|
||||
|
|
@ -47,9 +47,18 @@ By default it is not switched on. This enables folks to switch on the feature us
|
|||
* `Default` is usually set to `true` (see below)
|
||||
* `LockToDefault` is not set. Defaults to `false`
|
||||
|
||||
This enables the feature to be on and available in the default installation of Kubernetes.
|
||||
Beta features are usually on by default. This enables the feature to be available in the default installation of Kubernetes.
|
||||
|
||||
Sometimes (rarely) the `Default` is set to `false`. This tells folks that while this feature is in Beta, they will still need to do some work to switch it on and use it and potentially take some other explicit action outside of Kubernetes. For example, see the [CSIMigration feature gates](https://github.com/kubernetes/kubernetes/blob/5b0a2c3a29f6b5392e0f8f94ba5669bdc9eb73f6/pkg/features/kube_features.go#L792).
|
||||
Sometimes (rarely) the `Default` is set to `false` in Beta. This tells folks that while this feature is Beta, they will still need to do some work to switch it on and use it, and potentially take some other explicit action outside of Kubernetes. For example, the CSIMigration feature gates looked like this:
|
||||
|
||||
```
|
||||
CSIMigration: {Default: true, PreRelease: featuregate.Beta},
|
||||
CSIMigrationGCE: {Default: false, PreRelease: featuregate.Beta}, // Off by default (requires GCE PD CSI Driver)
|
||||
CSIMigrationAWS: {Default: false, PreRelease: featuregate.Beta}, // Off by default (requires AWS EBS CSI driver)
|
||||
CSIMigrationAzureDisk: {Default: false, PreRelease: featuregate.Beta}, // Off by default (requires Azure Disk CSI driver)
|
||||
CSIMigrationAzureFile: {Default: false, PreRelease: featuregate.Beta}, // Off by default (requires Azure File CSI driver)
|
||||
CSIMigrationvSphere: {Default: false, PreRelease: featuregate.Beta}, // Off by default (requires vSphere CSI driver)
|
||||
```
|
||||
|
||||
## GA Features
|
||||
|
||||
|
|
@ -57,19 +66,22 @@ Sometimes (rarely) the `Default` is set to `false`. This tells folks that while
|
|||
* `Default` is always set to `true`
|
||||
* `LockToDefault` is set to `true`
|
||||
|
||||
GA features are always on.
|
||||
GA features are always on by default, and usually cannot be disabled.
|
||||
|
||||
Sometimes (rarely) we do not set `LockToDefault` and let it default to `false`. This enables folks to switch off the GA feature. We do this to tell folks that while the feature (for example `coredns`) is GA, they need to move off say `kubedns` to `coredns` in their infrastructures pretty soon and if they want to continue `kubedns` for a short time, they will have to switch off the GA flag. When we do remove the support for `kubedns` entirely we would set `LockToDefault` to `true` with some grace period for the transition.
|
||||
Sometimes (rarely) we do not set `LockToDefault` (thus defaulting to `false`, meaning "not locked"). This enables folks to switch off the GA feature. We do this to indicate that while the feature (for example `coredns`) is GA, they need to move off `kubedns` to `coredns` in their infrastructure. If they want to continue using `kubedns` for a short time, they can choose to switch off the GA flag. When we eventually remove the support for `kubedns` entirely we would set `LockToDefault` to `true` with some grace period for the transition.
|
||||
|
||||
[After at least two releases post-GA and deprecation](https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecation), the feature gate is removed. Typically, we add a comment in [kubefeatures.go](https://github.com/kubernetes/kubernetes/blob/master/pkg/features/kube_features.go) such as: `// remove in 1.23` to signal when we plan to remove the feature gate. Remember when the feature gate is removed and the deployer has forgotten to drop the reference to the feature in the CLI flags (say the `kube-apiserver`), then they will see a hard failure.
|
||||
[After at least two releases post-GA and deprecation](https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecation), the feature gate is removed. Typically, we add a comment in [kubefeatures.go](https://github.com/kubernetes/kubernetes/blob/master/pkg/features/kube_features.go) such as: `// remove in 1.23` to signal when we plan to remove the feature gate. Remember when the feature gate is removed and the deployer has forgotten to drop the reference to the feature in the CLI flags (say the `kube-apiserver`), then they will see a hard failure.
|
||||
|
||||
Also note that when we set `LockToDefault` to `true`, we remove all references (if/then conditions) to the feature gate from the codebase.
|
||||
Also note that when we set `LockToDefault` to `true`, we remove all references (if/then conditions) to the feature gate from the codebase.
|
||||
|
||||
## Deprecation
|
||||
|
||||
* `PreRelease` is set to `featuregate.Deprecated`
|
||||
* `Default` is set to `false`
|
||||
* See [Kubernetes Deprecation Policy](https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecation) for more details
|
||||
|
||||
Very rarely we will deprecate some aspect of Kubernetes (almost always something that has no actual impact). When we do that, the pattern is to name the gate so it describes the functionality being deprecated and to default the value to `false`. If some user is impacted by the deprecation, they can set that gate to `true` to unbreak themselves (and then file a bug). If this happens, we must reconsider the deprecation and may choose to abandon it entirely by changing the gate back to `true` for a release or two and eventually removing it.
|
||||
|
||||
## Other scenarios
|
||||
|
||||
Sometimes we use`{Default: true, PreRelease: featuregate.Beta}` for keeping legacy behavior on while a new alternative is being implemented. When the new default behavior is transitioning to GA and it is time to drop the old legacy behavior, we will end up with `{Default: false, PreRelease: featuregate.GA, LockToDefault: true}`. For an example, see: [LegacyNodeRoleBehavior & ServiceNodeExclusion](https://github.com/kubernetes/kubernetes/pull/97543/files).
|
||||
|
|
|
|||
|
|
@ -62,6 +62,9 @@ your case by supplementing your PR with e.g.,
|
|||
- Key stakeholder SIG reviewers/approvers attesting to their confidence in the
|
||||
change being a required backport
|
||||
|
||||
To illustrate the point, dependency updates that just aim to silence some scanners
|
||||
and do not fix any vulnerable code are NOT eligible for cherry-picks.
|
||||
|
||||
If the change is in cloud provider-specific platform code (which is in the
|
||||
process of being moved out of core Kubernetes), describe the customer impact,
|
||||
how the issue escaped initial testing, remediation taken to prevent similar
|
||||
|
|
|
|||
|
|
@ -640,7 +640,7 @@ A quick overview of how we run e2e CI on Kubernetes.
|
|||
|
||||
### What is CI?
|
||||
|
||||
We run a battery of [release-blocking jobs](https://k8s-testgrid.appspot.com/sig-release-master-blocking)
|
||||
We run a battery of [release-blocking jobs](https://testgrid.k8s.io/sig-release-master-blocking)
|
||||
against `HEAD` of the master branch on a continuous basis, and block merges
|
||||
via [Tide](https://git.k8s.io/test-infra/prow/cmd/tide) on a subset of those
|
||||
tests if they fail.
|
||||
|
|
|
|||
|
|
@ -10,8 +10,15 @@ writing our tests defensively. When flakes are identified, we should prioritize
|
|||
addressing them, either by fixing them or quarantining them off the critical
|
||||
path.
|
||||
|
||||
For more information about deflaking Kubernetes tests, watch @liggitt's
|
||||
[presentation from Kubernetes SIG Testing - 2020-08-25](https://www.youtube.com/watch?v=Ewp8LNY_qTg).
|
||||
The project has a "zero-flake" policy. Test jobs must not automatically retry on test failures.
|
||||
This was announced and implemented in effect from 2019:
|
||||
[No more ginkgo.flakeAttempts=2 for e2e tests as of 2019-12-13](https://groups.google.com/g/kubernetes-dev/c/NNmEGUsJObg/m/dmI2mVc_AAAJ)
|
||||
(and then confirmed as policy in 2023).
|
||||
|
||||
For more information about deflaking Kubernetes tests, you can watch:
|
||||
- @liggitt's [presentation from Kubernetes SIG Testing - 2020-08-25](https://www.youtube.com/watch?v=Ewp8LNY_qTg).
|
||||
- @aojea's [presentation from Kubernetes SIG Testing - 2022-11-15](https://www.youtube.com/watch?v=x2Lj-ldR0AA&t=2660s).
|
||||
- @aojea's [Contributor Summit: "The art of deflaking Kubernetes tests"](https://sched.co/1LXGm).
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
|
|
|
|||
|
|
@ -78,8 +78,6 @@ better.
|
|||
|
||||
### Workflow
|
||||
|
||||
- [Gubernator Dashboard] - View incoming and outgoing Pull Requests that require
|
||||
your attention.
|
||||
- [Prow] - Kubernetes CI/CD System.
|
||||
- [Tide] - Prow plugin that manages merges and tests. [Tide Dashboard]
|
||||
- [Bot commands] - Commands used to interact with Kubernetes Bots (examples:
|
||||
|
|
@ -140,7 +138,7 @@ When closing a PR, convey an explanatory and cordial message explaining
|
|||
why it does not meet the requirements to be merged.
|
||||
|
||||
🙂 “I’m closing this PR because this feature can’t support the use case X. In
|
||||
it's proposed form, it would be a better to be implemented with Y tool. Thank
|
||||
its proposed form, it would be better to implement with Y tool. Thank
|
||||
you for working on this.”
|
||||
|
||||
😞 “Why isn’t this following the API conventions? This should be done elsewhere!”
|
||||
|
|
@ -153,7 +151,7 @@ why it does not meet the requirements to be merged.
|
|||
|
||||
Before you can submit a contribution, you must [sign the Contributor License
|
||||
Agreement(CLA)][cla]. The Kubernetes project can _only_ accept a contribution
|
||||
if you or your company has signed the CLA.
|
||||
if you or your company have signed the CLA.
|
||||
|
||||
Should you encounter any problems signing the CLA, follow the [CLA
|
||||
troubleshooting guidelines].
|
||||
|
|
@ -164,7 +162,7 @@ troubleshooting guidelines].
|
|||
GitHub Issues are the primary means of tracking things such as bug reports,
|
||||
enhancement requests, or reporting other issues such as failing tests. They are
|
||||
**not** intended for [user support requests]. For those, please check with the
|
||||
[troubleshooting guide], report the problem to [Stack Overflow] or follow up on
|
||||
[troubleshooting guide], report the problem to [Stack Overflow], or follow up on
|
||||
the [Kubernetes forum].
|
||||
|
||||
**References:**
|
||||
|
|
@ -212,8 +210,8 @@ other forms of work that would be stored within a git repository.
|
|||
#### Creating a Pull Request
|
||||
|
||||
- Follow the directions of the pull request template if one is available. It
|
||||
will help those that respond to your PR.
|
||||
- If a [trivial fix] such as a broken link, typo or grammar mistake, review the
|
||||
will help those who respond to your PR.
|
||||
- If a [trivial fix] such as a broken link, typo, or grammar mistake, review the
|
||||
entire document for other potential mistakes. Do not open multiple PRs for
|
||||
small fixes in the same document.
|
||||
- Reference any issues related to your PR, or issues that PR may solve.
|
||||
|
|
@ -250,11 +248,11 @@ What's in that PR:
|
|||
- **Line 1** - Reference to other issues or PRs (#3064 #3097).
|
||||
- **Line 2** - A brief description of what is being done in the PR.
|
||||
- **Line 4** - [SIG][sigs] assignment with the [command][commands]
|
||||
`/sig contributor-experience`..
|
||||
- **Line 5** - Reviewers that may have interest on this specific issue or PR are
|
||||
`/sig contributor-experience`.
|
||||
- **Line 5** - Reviewers that may have interest in this specific issue or PR are
|
||||
specified with the [`/cc`][cc] command.
|
||||
- **Line 6** - The [`/kind cleanup`][kind] command add a [label][labels] that
|
||||
categorizes issue or PR as related to cleaning up code, process, or technical
|
||||
- **Line 6** - The [`/kind cleanup`][kind] command adds a [label][labels] that
|
||||
categorizes issues or PR as related to cleaning up code, process, or technical
|
||||
debt.
|
||||
- **Line 7** - The [`/area developer-guide`][kind] command categorizes issue or
|
||||
PR as related to the developer guide.
|
||||
|
|
@ -272,7 +270,7 @@ will reply to the PR with links to the failed tests and available logs.
|
|||
|
||||
Pushing new commits to your PR will automatically trigger the tests to re-run.
|
||||
|
||||
Occasionally there can be issues with Kubernetes CI platform. These can occur
|
||||
Occasionally there can be issues with the Kubernetes CI platform. These can occur
|
||||
for a wide variety of reasons even if your contribution passes all local
|
||||
tests. You can trigger a re-run of the tests with the `/retest` command.
|
||||
|
||||
|
|
@ -327,7 +325,7 @@ configured within your local working copy.
|
|||
Add `upstream` as a remote, and configure it so you cannot push to it.
|
||||
|
||||
```
|
||||
# replace <upstream git repo> with the upstream repo url
|
||||
# replace <upstream git repo> with the upstream repo URL
|
||||
# example:
|
||||
# https://github.com/kubernetes/kubernetes.git
|
||||
# git@github.com/kubernetes/kubernetes.git
|
||||
|
|
@ -362,9 +360,9 @@ git checkout -b myfeature
|
|||
#### Squashing Commits
|
||||
|
||||
The main purpose of [squashing commits] is to create a clean readable git
|
||||
history or log of the changes that were made. Usually this is done in last
|
||||
history or log of the changes that were made. Usually, this is done in the last
|
||||
phase of a PR revision. If you are unsure if you should squash your commits, it
|
||||
is better to err on the side of having more and leave it up to the judgement of
|
||||
is better to err on the side of having more and leave it up to the judgment of
|
||||
the other contributors assigned to review and approve your PR.
|
||||
|
||||
Perform an interactive rebase to choose which commits you want to keep and which you want to squash, then force push your branch:
|
||||
|
|
@ -380,7 +378,6 @@ git push --force
|
|||
[contributor course]: https://www.kubernetes.dev/docs/onboarding
|
||||
[contributor guide]: /contributors/guide/README.md
|
||||
[developer guide]: /contributors/devel/README.md
|
||||
[gubernator dashboard]: https://gubernator.k8s.io/pr
|
||||
[prow]: https://prow.k8s.io
|
||||
[tide]: http://git.k8s.io/test-infra/prow/cmd/tide/pr-authors.md
|
||||
[tide dashboard]: https://prow.k8s.io/tide
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ description: |
|
|||
## Find something to work on
|
||||
|
||||
The first step to getting starting contributing to Kubernetes is to find something
|
||||
to work on. Help is always welcome, and no contribution is too small!
|
||||
to work on. Help is always welcome, and no contribution is too small (but see below)!
|
||||
|
||||
Here are some things you can do today to get started contributing:
|
||||
|
||||
|
|
@ -34,6 +34,12 @@ If the above suggestions don't appeal to you, you can browse the
|
|||
in contributing without writing code can also find ideas in the
|
||||
[Non-Code Contributions Guide].
|
||||
|
||||
*Note*: although contributions are welcome, beware that every pull
|
||||
request creates work for maintainers and costs for testing it.
|
||||
Fixing *linter warnings* is often *not* worth it because the
|
||||
existing code is fine. Always discuss with maintainers first
|
||||
before creating such PRs.
|
||||
|
||||
### Find a good first topic
|
||||
|
||||
There are [multiple repositories] within the Kubernetes organization.
|
||||
|
|
|
|||
|
|
@ -61,9 +61,9 @@ You can run these local verifications before you submit your pull request to pre
|
|||
|
||||
Merging a pull request requires the following steps to be completed before the pull request will be merged automatically.
|
||||
|
||||
- [Sign the CLA](https://git.k8s.io/community/CLA.md) (prerequisite)
|
||||
- [Open a pull request](https://help.github.com/articles/about-pull-requests/)
|
||||
- *For kubernetes/kubernetes repository only:* Add [release notes](/contributors/guide/release-notes.md) if needed.
|
||||
- Follow the EasyCLA steps to [sign the CLA](https://git.k8s.io/community/CLA.md) (prerequisite)
|
||||
- Pass all e2e tests
|
||||
- Get all necessary approvals from reviewers and code owners
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,8 @@
|
|||
stmcginnis,jameslaverack,pacoxu,rphitg00,sayanchowdhury,kalyan678,anammedina21,jeremyrickard,reylejano
|
||||
No opinion,3,No opinion,No opinion,2,No opinion,No opinion,1,4
|
||||
6,4,5,9,7,8,2,1,3
|
||||
8,3,5,9,8,7,2,1,4
|
||||
4,6,7,8,5,9,1,2,3
|
||||
9,4,6,8,5,7,3,1,2
|
||||
3,2,4,9,9,9,1,1,1
|
||||
7,6,3,8,5,9,2,1,2
|
||||
|
|
|
@ -0,0 +1,11 @@
|
|||
# Results of the 2023 Kubernetes Code of Conduct Committee Elections
|
||||
|
||||
- Number of seats open: 2 (2 year term)
|
||||
- Number of eligible voters: 7
|
||||
- Number of votes cast: 7
|
||||
- Turnout: 100%
|
||||
|
||||
## Winners
|
||||
|
||||
- Ana Margarita Medina
|
||||
- Jeremy Rickard
|
||||
|
|
@ -139,7 +139,7 @@ Examples of contributions that would NOT be considered:
|
|||
| Wednesday, September 27 | Private announcement of Results to SC members not up for election |
|
||||
| Sunday, October 1 | Private announcement of Results to all candidates |
|
||||
| Monday, October 2 | Public announcement of Results at Public Steering Committee Meeting |
|
||||
| Thursday, October 5 | Election Retro |
|
||||
| Tuesday, October 3 | Election Retro |
|
||||
|
||||
Candidate nomination, bio, and election close deadlines will be done using Anywhere on Earth timing, meaning it is still valid to submit new nominations/bios/votes as long as it is still the last day anywhere on the planet (i.e. at the end of that day in UTC-12).
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,210 @@
|
|||
detiber,vincepri,natalisucks,soltysh,qedrakmar,justaugustus,xmudrii,ameukam,divya-mohan0209,pohly,pacoxu
|
||||
4,2,11,1,11,11,11,11,3,11,11
|
||||
9,8,1,4,6,10,7,2,5,11,3
|
||||
6,11,3,9,1,2,7,5,4,11,11
|
||||
4,9,8,6,10,2,5,1,3,11,7
|
||||
11,11,11,11,11,11,11,11,11,11,11
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
11,11,11,11,11,11,11,11,11,11,11
|
||||
10,10,10,10,10,10,10,10,10,11,11
|
||||
11,11,11,1,11,11,5,5,2,3,4
|
||||
11,11,4,1,11,11,11,11,2,11,3
|
||||
11,3,11,11,11,11,11,1,11,2,11
|
||||
8,7,3,1,6,4,4,9,5,2,11
|
||||
5,2,No opinion,1,3,6,No opinion,No opinion,No opinion,4,No opinion
|
||||
No opinion,5,No opinion,1,7,3,No opinion,No opinion,4,6,2
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
11,11,11,11,11,11,11,11,11,1,1
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
3,11,2,7,5,1,8,6,4,9,10
|
||||
3,6,11,5,2,1,11,4,11,11,11
|
||||
11,3,11,2,11,4,11,11,11,1,11
|
||||
11,11,11,3,11,11,11,11,11,2,1
|
||||
5,5,11,2,5,4,3,5,11,1,11
|
||||
11,11,2,11,11,11,3,4,11,1,11
|
||||
3,1,11,11,11,2,5,11,11,4,11
|
||||
11,11,11,11,11,11,11,11,11,11,11
|
||||
5,2,No opinion,1,3,6,No opinion,No opinion,No opinion,4,No opinion
|
||||
3,2,10,9,6,5,7,11,8,4,1
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
3,11,11,11,11,2,11,1,11,11,11
|
||||
11,11,No opinion,1,No opinion,11,2,2,1,1,1
|
||||
8,5,6,4,11,1,9,10,2,7,3
|
||||
9,7,5,1,11,8,4,10,6,3,2
|
||||
11,11,11,11,11,11,11,11,9,11,1
|
||||
No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,9,11
|
||||
10,11,11,11,11,11,10,11,11,11,1
|
||||
11,11,11,3,11,2,11,11,11,1,11
|
||||
8,5,2,6,No opinion,No opinion,1,No opinion,7,4,3
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
11,11,11,2,11,3,11,11,11,4,1
|
||||
4,11,11,1,11,3,6,11,11,2,4
|
||||
7,3,11,4,9,8,6,5,10,2,1
|
||||
5,3,6,11,11,11,4,2,7,1,11
|
||||
11,11,10,2,11,8,11,5,11,1,6
|
||||
No opinion,No opinion,11,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,1
|
||||
2,5,3,8,7,1,9,6,4,11,10
|
||||
9,7,2,1,11,10,8,5,4,6,3
|
||||
No opinion,No opinion,No opinion,1,No opinion,2,3,No opinion,No opinion,4,5
|
||||
5,7,1,6,10,3,4,9,2,11,8
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
10,4,2,1,8,3,9,7,6,5,11
|
||||
8,9,7,4,1,10,2,11,3,6,5
|
||||
4,10,5,9,11,2,3,1,8,6,7
|
||||
3,10,1,6,8,2,7,5,4,11,9
|
||||
10,7,8,1,9,11,5,2,3,4,6
|
||||
No opinion,1,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion
|
||||
11,11,1,11,11,1,6,6,2,3,7
|
||||
4,No opinion,No opinion,1,6,2,7,No opinion,No opinion,5,3
|
||||
2,4,6,9,1,10,5,3,7,8,11
|
||||
5,4,11,2,6,10,3,8,9,1,7
|
||||
No opinion,1,No opinion,1,No opinion,1,No opinion,1,No opinion,No opinion,No opinion
|
||||
3,2,No opinion,No opinion,1,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion
|
||||
7,11,4,2,8,10,6,9,5,1,3
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
6,1,3,8,No opinion,2,4,9,7,No opinion,5
|
||||
5,1,11,2,10,3,8,4,9,7,6
|
||||
3,2,2,No opinion,No opinion,1,6,No opinion,1,4,5
|
||||
6,11,7,2,10,4,8,1,3,5,9
|
||||
No opinion,3,No opinion,1,No opinion,No opinion,No opinion,No opinion,No opinion,11,2
|
||||
11,1,11,11,11,11,11,11,11,11,11
|
||||
11,11,11,11,11,2,11,11,11,1,11
|
||||
7,9,3,8,5,6,1,2,4,11,10
|
||||
11,6,6,1,9,6,8,9,4,3,4
|
||||
11,No opinion,2,No opinion,No opinion,No opinion,3,4,1,No opinion,5
|
||||
4,10,2,1,9,11,7,3,8,5,6
|
||||
No opinion,No opinion,1,1,1,9,5,5,1,6,No opinion
|
||||
1,2,No opinion,5,No opinion,3,7,8,No opinion,6,4
|
||||
11,11,11,1,11,4,5,11,11,2,6
|
||||
4,2,1,11,11,11,11,11,3,11,11
|
||||
11,11,1,11,11,4,11,11,11,2,3
|
||||
No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,1,No opinion
|
||||
6,11,9,2,8,3,7,1,10,4,5
|
||||
No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,11
|
||||
5,3,7,9,10,11,8,4,2,6,1
|
||||
6,11,4,3,11,1,7,11,2,5,11
|
||||
11,11,11,1,11,5,3,2,6,7,3
|
||||
10,11,5,4,3,7,8,2,1,9,6
|
||||
11,11,11,11,11,11,11,2,11,1,3
|
||||
4,3,2,5,7,6,9,No opinion,1,8,No opinion
|
||||
8,9,4,6,10,11,7,2,1,3,5
|
||||
11,11,11,1,11,11,11,11,11,11,11
|
||||
5,5,2,1,5,11,3,4,3,4,4
|
||||
No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,11,No opinion
|
||||
11,10,4,2,5,6,9,7,8,3,1
|
||||
6,9,6,1,3,4,5,7,8,2,4
|
||||
11,7,11,2,9,11,11,11,8,3,1
|
||||
11,11,11,11,11,6,11,2,2,3,1
|
||||
10,11,5,7,9,4,6,2,8,3,1
|
||||
3,11,11,5,6,10,11,1,10,8,4
|
||||
3,11,11,11,11,11,4,1,11,2,11
|
||||
No opinion,3,No opinion,No opinion,No opinion,No opinion,4,2,1,No opinion,No opinion
|
||||
11,1,11,1,11,11,11,11,11,11,11
|
||||
11,11,11,1,2,11,11,3,11,11,4
|
||||
8,6,2,4,10,11,9,1,3,5,7
|
||||
11,5,No opinion,No opinion,6,1,4,3,2,No opinion,No opinion
|
||||
9,7,11,5,11,11,9,11,11,1,5
|
||||
3,3,1,2,3,3,3,1,1,2,2
|
||||
11,6,2,1,10,9,8,7,3,4,5
|
||||
4,7,5,1,6,3,3,2,2,4,5
|
||||
6,2,10,4,11,1,5,7,9,3,8
|
||||
11,11,11,11,11,4,2,1,11,3,5
|
||||
No opinion,No opinion,No opinion,1,No opinion,2,No opinion,No opinion,No opinion,No opinion,No opinion
|
||||
No opinion,No opinion,No opinion,No opinion,No opinion,2,No opinion,No opinion,No opinion,1,3
|
||||
11,2,11,1,11,5,11,11,11,4,3
|
||||
11,11,4,1,11,11,11,11,11,4,4
|
||||
3,9,2,9,4,1,5,4,3,11,11
|
||||
6,11,1,2,11,4,11,5,11,5,3
|
||||
8,6,11,1,11,5,4,7,11,2,3
|
||||
4,8,11,8,11,4,4,1,2,11,11
|
||||
2,3,No opinion,1,No opinion,No opinion,No opinion,No opinion,No opinion,4,No opinion
|
||||
9,10,1,3,5,2,7,4,8,11,6
|
||||
No opinion,3,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,1
|
||||
7,6,8,5,10,4,9,1,2,3,11
|
||||
11,11,11,1,11,11,11,2,3,11,4
|
||||
4,6,10,1,9,7,11,3,8,2,5
|
||||
5,6,11,1,8,7,4,9,10,2,3
|
||||
No opinion,No opinion,No opinion,11,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion
|
||||
11,10,11,1,11,11,11,11,11,5,11
|
||||
No opinion,No opinion,No opinion,11,No opinion,No opinion,No opinion,No opinion,11,No opinion,No opinion
|
||||
3,10,2,1,11,10,10,1,2,10,4
|
||||
10,9,7,6,1,11,8,2,5,3,4
|
||||
11,1,11,1,11,11,11,11,11,11,11
|
||||
11,11,11,11,11,11,11,11,11,1,1
|
||||
11,2,3,11,11,8,3,11,11,11,1
|
||||
11,11,11,1,11,11,1,11,11,1,1
|
||||
4,6,2,9,3,11,10,5,1,8,7
|
||||
11,11,11,11,11,11,11,11,11,11,11
|
||||
2,11,11,3,11,1,11,11,11,11,11
|
||||
11,3,11,1,11,11,2,11,11,11,4
|
||||
11,10,11,2,11,3,4,11,11,1,11
|
||||
No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion
|
||||
No opinion,No opinion,No opinion,2,No opinion,No opinion,No opinion,No opinion,No opinion,1,No opinion
|
||||
11,4,8,2,10,1,5,7,9,3,6
|
||||
8,1,6,9,7,3,5,2,10,4,11
|
||||
No opinion,No opinion,No opinion,1,No opinion,1,2,2,1,2,No opinion
|
||||
11,2,11,1,11,11,11,11,11,11,3
|
||||
3,11,11,11,2,1,11,4,11,11,11
|
||||
No opinion,4,No opinion,1,6,3,7,No opinion,5,2,No opinion
|
||||
4,1,No opinion,4,No opinion,2,No opinion,6,No opinion,5,3
|
||||
7,9,2,1,11,10,6,4,5,3,8
|
||||
7,10,2,1,11,9,4,5,6,8,3
|
||||
5,11,3,2,11,7,7,1,6,4,1
|
||||
7,9,3,2,11,6,1,4,5,10,8
|
||||
10,11,10,1,10,10,2,10,10,10,10
|
||||
6,11,3,1,11,11,11,2,5,11,4
|
||||
11,7,4,1,2,5,9,10,8,3,6
|
||||
2,10,7,1,7,11,4,9,3,8,10
|
||||
11,11,4,2,11,5,1,4,5,5,3
|
||||
No opinion,No opinion,No opinion,1,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion
|
||||
11,11,11,5,11,3,11,11,4,2,1
|
||||
11,5,11,2,11,4,11,11,11,1,3
|
||||
No opinion,2,No opinion,1,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,No opinion
|
||||
11,11,11,11,11,5,11,11,11,11,11
|
||||
11,4,11,11,11,1,11,11,2,3,5
|
||||
10,9,1,8,7,6,5,11,3,4,2
|
||||
2,No opinion,3,No opinion,2,No opinion,2,2,1,1,No opinion
|
||||
10,6,1,8,5,4,11,2,3,9,7
|
||||
5,11,3,11,11,1,6,2,4,11,11
|
||||
4,5,9,10,7,1,6,2,3,8,11
|
||||
6,11,11,1,11,8,3,11,4,2,11
|
||||
6,11,7,1,9,2,8,10,5,3,4
|
||||
4,2,4,1,11,3,4,4,4,4,4
|
||||
3,1,10,7,6,11,4,2,8,5,9
|
||||
4,5,9,10,7,1,6,2,3,8,11
|
||||
1,7,6,4,9,5,8,11,1,3,10
|
||||
11,7,11,6,5,11,2,4,11,3,1
|
||||
11,3,9,1,10,5,4,6,8,2,7
|
||||
2,10,3,4,8,11,5,9,2,6,7
|
||||
11,6,11,1,11,11,11,11,11,11,11
|
||||
1,2,No opinion,4,No opinion,3,No opinion,No opinion,No opinion,No opinion,No opinion
|
||||
No opinion,No opinion,No opinion,No opinion,No opinion,No opinion,11,11,8,8,No opinion
|
||||
No opinion,No opinion,4,1,No opinion,2,No opinion,No opinion,4,2,2
|
||||
11,11,11,11,11,11,11,11,1,11,11
|
||||
11,11,11,11,11,2,11,11,11,1,3
|
||||
No opinion,No opinion,No opinion,No opinion,No opinion,1,No opinion,No opinion,2,No opinion,No opinion
|
||||
2,3,11,1,11,11,11,6,11,5,4
|
||||
8,7,2,1,11,5,4,6,9,3,10
|
||||
6,2,5,1,4,8,9,10,7,3,11
|
||||
6,9,4,2,8,1,10,7,3,11,5
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
1,11,11,11,11,11,11,11,11,11,11
|
||||
11,11,4,2,11,11,11,5,1,3,6
|
||||
No opinion,No opinion,No opinion,No opinion,No opinion,3,1,No opinion,2,No opinion,No opinion
|
||||
No opinion,No opinion,1,1,No opinion,No opinion,1,No opinion,1,No opinion,No opinion
|
||||
4,7,6,5,7,1,5,3,5,6,2
|
||||
11,11,11,11,11,11,11,11,11,11,1
|
||||
11,11,11,11,11,3,11,11,11,2,1
|
||||
11,11,1,11,11,11,11,2,11,11,11
|
||||
4,8,7,10,6,2,3,5,1,11,9
|
||||
4,8,7,1,9,2,10,11,5,3,6
|
||||
11,1,2,3,11,11,5,11,11,6,4
|
||||
11,3,9,1,2,8,10,4,5,6,7
|
||||
9,11,1,4,6,10,7,2,3,10,5
|
||||
2,5,1,8,10,3,9,7,4,6,11
|
||||
2,9,3,6,10,5,7,5,8,1,4
|
||||
11,11,2,11,11,6,4,5,1,4,3
|
||||
5,2,11,3,11,6,2,1,11,4,8
|
||||
3,No opinion,1,No opinion,6,2,No opinion,2,1,No opinion,No opinion
|
||||
|
|
|
@ -0,0 +1,41 @@
|
|||
-------------------------------------------------------------
|
||||
name: Arnaud Meukam
|
||||
ID: ameukam
|
||||
info:
|
||||
- employer: VMware
|
||||
- slack: Arnaud
|
||||
-------------------------------------------------------------
|
||||
|
||||
## SIGS
|
||||
|
||||
- SIG K8s Infra: SIG Chair
|
||||
- SIG Release: Release Manager Associate
|
||||
- SIG Testing
|
||||
|
||||
## What I have done
|
||||
|
||||
I have been involved with the Kubernetes project since 2018. Joined as a shadow in the SIG Release shadow program. I later joined the Kubernetes Infrastructure SIG and became SIG Chair.
|
||||
|
||||
- Boostrap registry.k8s.io as the new distribution platform for our container images
|
||||
- Establish a partnership with Fastly to ensure our binaries to distributed to a CDN network.
|
||||
- Driving the strategy on how to extend our infrastructure footprint to AWS
|
||||
- Member of the past release teams (1.12, 1.13, 1.14)
|
||||
- Former Github Admin for all organizations of the projects
|
||||
|
||||
## What I'll do
|
||||
|
||||
As a member of the community, I am committed to pushing the project's progress while preserving the community's ideals. My primary goal is to keep Kubernetes at the cutting edge of innovation while retaining a user-centric approach. I will work relentlessly to encourage collaboration among all stakeholders, empowering developers, operators, and end users alike.
|
||||
|
||||
I am passionate about making Kubernetes more accessible to newcomers, streamlining the onboarding process. Additionally, I will champion initiatives that prioritize sustainability and efficiency, ensuring Kubernetes remains a sustainable choice for organizations of all sizes.
|
||||
|
||||
I will advocate for strategic decisions that align with both the project's technical excellence and its broader impact on the cloud-native ecosystem. Through transparent communication, active engagement with the community, and a commitment to inclusivity, I aim to drive Kubernetes forward as a powerful and versatile platform that meets the evolving needs of the industry.
|
||||
|
||||
In collaboration with my fellow committee members, I will work to nurture a culture of diversity, and collaboration, ensuring that Kubernetes continues to thrive as an open-source project.
|
||||
|
||||
## Resources About Me
|
||||
|
||||
- Twitter: [@ameukam](https://twitter.com/ameukam)
|
||||
- Talks:
|
||||
- [Why We Moved the Kubernetes Image Registry](https://www.youtube.com/watch?v=9CdzisDQkjE)
|
||||
- [KCNA 22 - Kubernetes Infra SIG: Intro And Updates](https://www.youtube.com/watch?v=mJAC4asDCOw)
|
||||
- [KCEU 23 - Kubernetes Infra SIG: Intro And Updates](https://www.youtube.com/watch?v=_QAElyKyN1o)
|
||||
|
|
@ -0,0 +1,53 @@
|
|||
-------------------------------------------------------------
|
||||
name: Jason DeTiberus
|
||||
ID: detiber
|
||||
info:
|
||||
- employer: Cisco
|
||||
- slack: jdetiber
|
||||
-------------------------------------------------------------
|
||||
|
||||
## SIGS
|
||||
|
||||
- SIG Release
|
||||
- v1.9 Release Team: Upgrade Testing / CI Signal Shadow
|
||||
- v1.14 Release Team: Branch Manager Shadow
|
||||
- SIG Contributor Experience
|
||||
- 2019 NA Contrib Summit SIG Meet & Greet Shadow
|
||||
- 2020 EU Contrib Summit SIG Meet & Greet Lead (unfortunately cancelled )
|
||||
- 2022 NA Contrib Summit Content Lead
|
||||
- 2023 EU Contrib Summit Content Lead
|
||||
- SIG Beard Technical Lead
|
||||
|
||||
## What I have done
|
||||
|
||||
I have been involved in the greater Kubernetes community since 2015. Most folks likely know me through the work that I've done in SIG Cluster Lifecycle and Cluster API, where I lead the development of features and improvements unlocking real world production use.
|
||||
|
||||
More importantly, I was instrumental in expanding and growing the community around the Cluster API project. This included breaking down barriers between competing projects, vendor products, end users, and individual contributors. As a result, bringing the wide scale adoption of Cluster API as the defacto standard for building Kubernetes lifecycle management tooling.
|
||||
|
||||
Over the years, I have sought out ways to contribute back to the community, this includes serving on the Program Committee for KubeCon/CloudNativeCon, assisting with Kubernetes Contributor Summits, and most recently serving as a member of the Code of Conduct Committee.
|
||||
|
||||
### Emeritus roles
|
||||
|
||||
- Kubernetes Code of Conduct Committee
|
||||
- [Cluster API](https://github.com/kubernetes-sigs/cluster-api) maintainer
|
||||
- [Cluster API Provider AWS](https://github.com/kubernetes-sigs/cluster-api-provider-aws) maintainer
|
||||
- [Cluster API Provider GCP](https://github.com/kubernetes-sigs/cluster-api-provider-gcp) maintainer
|
||||
- [Cluster API Provider Packet](https://github.com/kubernetes-sigs/cluster-api-provider-packet) maintainer
|
||||
|
||||
## What I'll do
|
||||
|
||||
The biggest challenge that Kubernetes faces as a project is sustainability, and that is my top priority. I see this as a three pronged approach:
|
||||
|
||||
- Sustainability of Maintainers: ensuring that we have appropriate programs in place for mentorship, growth, and avoiding maintainer burnout.
|
||||
- Sustainability of Contributors: ensuring that we are implementing processes to reduce the barrier to entry for new contributors and that we are actively fostering a diverse inclusive, and supportive environment for all contributors.
|
||||
- Sustainability of Infrastructure: ensuring that we can head off future funding emergencies related to running the project infrastructure, that funding is not reliant on a single company, and we secure long term commitments for funding.
|
||||
|
||||
## Resources About Me
|
||||
|
||||
- [GitHub](https://github.com/detiber)
|
||||
- [LinkedIn](https://www.linkedin.com/in/detiber)
|
||||
- [X (Twitter)](https://twitter.com/detiber)
|
||||
- [Mastodon](https://hachyderm.io/@detiber)
|
||||
- [BlueSky](https://bsky.app/profile/jason.detiber.us)
|
||||
- [YouTube (talk playlist)](https://youtube.com/playlist?list=PL7PQoVTdHM_S8G9OtYWFcLWRkwZakbXOW)
|
||||
|
||||
|
|
@ -0,0 +1,60 @@
|
|||
-------------------------------------------------------------
|
||||
name: Stephen Augustus
|
||||
ID: justaugustus
|
||||
info:
|
||||
- employer: Cisco
|
||||
- slack: justaugustus
|
||||
-------------------------------------------------------------
|
||||
|
||||
## SIGs
|
||||
|
||||
- SIG Release
|
||||
- SIG Release Chair
|
||||
- Release Manager
|
||||
- Release Engineering subproject owner
|
||||
|
||||
## External open source roles
|
||||
|
||||
- OpenSSF Governing Board member
|
||||
- OpenAPI Initiative Business Governing Board member
|
||||
- Maintainer:
|
||||
- [OpenSSF Scorecard](https://github.com/ossf/scorecard)
|
||||
- [CNCF Dex](https://dexidp.io/)
|
||||
|
||||
## What I have done
|
||||
|
||||
Throughout my career in Kubernetes, I have identified and contributed to high-impact areas of the project, founded, staffed, and mentored multiple governance groups, and created process and policy in its absence.
|
||||
|
||||
### Emeritus roles
|
||||
|
||||
- SIG PM Chair
|
||||
- SIG Azure Chair
|
||||
- WG Naming Lead
|
||||
- [Cluster API Azure][capz] maintainer (SIG Cluster Lifecycle)
|
||||
- [Enhancements][enhancements] subproject owner (SIG Architecture)
|
||||
- [New Membership Coordinator][nmc] (GitHub Management subproject)
|
||||
- Release Team member
|
||||
|
||||
## What I'll do
|
||||
|
||||
My continued goal is to **_reduce/remove friction in contributing to Kubernetes._**
|
||||
|
||||
To help ensure the **sustainability** of the project, I will focus on three areas; _effectiveness_, _agility_, and _sponsorship_:
|
||||
|
||||
Supporting initiatives that bolster the **Effectiveness** of our governance bodies, both in actuality and community perception.
|
||||
|
||||
Improve mechanisms to achieve quality decisions, without sacrificing **Agility**.
|
||||
|
||||
**Sponsorship** of efforts that allow community members to sustain contributions to the Kubernetes project and the wider ecosystem.
|
||||
|
||||
## Resources About Me
|
||||
|
||||
- [whois.auggie.dev (personal website)](https://whois.auggie.dev/)
|
||||
- [GitHub](https://github.com/justaugustus)
|
||||
- [LinkedIn](https://www.linkedin.com/in/stephenaugustus)
|
||||
- [X (Twitter)](https://twitter.com/stephenaugustus)
|
||||
- [YouTube (talk playlist)](https://youtube.com/playlist?list=PLnRXOw13j0MsfAinWbb1AJ5b9CAx9uBNM)
|
||||
|
||||
[capz]: https://sigs.k8s.io/cluster-api-provider-azure
|
||||
[enhancements]: https://git.k8s.io/community/sig-architecture#enhancements
|
||||
[nmc]: https://git.k8s.io/community/github-management#new-membership-coordinator
|
||||
|
|
@ -0,0 +1,43 @@
|
|||
-------------------------------------------------------------
|
||||
name: Natali Vlatko
|
||||
ID: natalisucks
|
||||
info:
|
||||
- employer: Cisco
|
||||
- slack: Natali
|
||||
-------------------------------------------------------------
|
||||
|
||||
## SIGS
|
||||
|
||||
- SIG Docs / Co-Chair
|
||||
- SIG Auth / Issue Triage
|
||||
|
||||
## What I have done
|
||||
|
||||
I've served as the Co-Chair of SIG Docs since early 2022, with my involvement in the overall project beginning in 2020 via SIG Docs and SIG Auth. I'm a newer community member amongst most maintainers, however, I'd still like to share my humble list of high-fives:
|
||||
|
||||
- I helped launch the official Localization Subproject for Kubernetes, which earned me the [2021 Kubernetes Contributor Award](https://www.kubernetes.dev/community/awards/2021/) for SIG Docs. Kubernetes documentation is now available in 15 different languages. I've continued to work on improving localization processes for better language onboarding, plus greater recognition of localization contributions for Kubernetes organization membership
|
||||
- I co-sponsored our PR Wrangler Shadow Program in SIG Docs, where contributors learn how approvers of the SIG action PRs through various tooling and workflows. This program created better visibility into the reponsibilities of reviewers and approvers, and has grown the reviewers and approvers group
|
||||
- I helped launch the regular issue triage sessions for SIG Auth, which I still participate in today. This triaging helped SIG Auth organize work on various KEPs, such as [improvements to the Key Management Service (KMS) API](https://kubernetes.io/blog/2022/09/09/kms-v2-improvements/), and fostered better in-roads for new contributors to participate in the SIG
|
||||
- I've volunteered for several Kubernetes Contributor Summits, recently as a Registration and Day-Of Ops shadow for the 2023 EU edition, and will be leading Day-Of Operations for the upcoming Kubernetes Contributor Summit NA 2023
|
||||
- Across the greater CNCF landscape, I've served on the Program Committee for both KubeCon/CloudNativeCon and Open Source Summit for several years and continue to do so
|
||||
|
||||
## What I'll do
|
||||
|
||||
As a contributor, maintainer, and now co-chair of SIG Docs, I've experienced each segment of the new contributor journey, where we see some of the largest numbers of first-time PRs to the project from new contributors. Sustaining these contributions has been part of my ongoing co-chair responsibilities, and in working with other co-chairs across SIGs, we all recognize that sustainability across contribution types for Kubernetes is _hard_. To address this in the Steering Committee, I want help foster investment into Kubernetes contributions via CNCF sponsorship, and partner with CNCF Members across all levels to build pathways for part-time and full-time Kubernetes maintainers.
|
||||
|
||||
I also want the Steering Committee to be geographically diverse, so that it represents how global our project is, and how distinct our contributors are. I believe we should have representation from other contributor regions, such as EMEA and APAC, so that their challenges with the project can be addressed at the highest tier. To achieve this, folks like myself need to stand for nomination, so that this diverse representation can be achieved. Kubernetes, via Steering, will benefit from the rich differences in culture, experience, and perspectives that a globally diverse cohort can bring to decision-making and guideance of the project and its values.
|
||||
|
||||
Finally, I'd like to focus on Kubernetes governance, where the project has become large enough to serve as an example for others to follow. As the flagship project of the CNCF, Kubernetes governance should be the epitome of efficiency, transparency, and fairness; I want to bring more awareness and outward communication of the decision-making of Steering, and seek out and apply (where possible) community feedback to current processes of the Committee. I want to take this focus so that our community knows and understands the role of the Steering Committee and how it should ultimately serve them.
|
||||
|
||||
## Resources About Me
|
||||
|
||||
- My academic background and current career converged at Write The Docs Prague 2020 with my favorite talk to date:
|
||||
- [Documenting the (Ancient) History of Your Project](https://www.youtube.com/watch?v=YxNx9Fi40-Y&list=PLZAeFn6dfHpmRWZJaUwQzsdagW2TtRI2x&index=5)
|
||||
- Some of my KubeCon/CloudNativeCon talks:
|
||||
- [How To Localize Kubernetes Documentation: A Guide For Everyone (KubeCon/CloudNativeCon EU 2023)](https://kccnceu2023.sched.com/event/1HyUP)
|
||||
- [Contributing to the Kubernetes Website: A Guide For Everyone (KubeCon/CloudNativeCon NA 2022)](https://kccncna2022.sched.com/event/182O1/contributing-to-the-kubernetes-website-a-guide-for-everyone-divya-mohan-rey-lejano-suse-tim-bannister-the-scale-factory-natali-vlatko-wayfair-arsh-sharma-okteto)
|
||||
- Myself and Celeste Horgan at 2023's Berlin Buzzwords (and coming up at Open Source Summit EU 2023):
|
||||
- [Building On-Ramps for Non-Code Contributors in Open Source](https://program.berlinbuzzwords.de/berlin-buzzwords-2023/talk/VEQHVW/)
|
||||
- Find me on [GitHub](https://github.com/natalisucks)
|
||||
- Check out my [LinkedIn](https://www.linkedin.com/in/natalivlatko)
|
||||
- Scroll through my [Twitter](https://twitter.com/natalisucks)
|
||||
|
|
@ -0,0 +1,67 @@
|
|||
-------------------------------------------------------------
|
||||
name: Patrick Ohly
|
||||
ID: pohly
|
||||
info:
|
||||
- employer: Intel Corporation
|
||||
- slack: pohly
|
||||
-------------------------------------------------------------
|
||||
|
||||
## SIGS
|
||||
|
||||
- SIG Testing technical lead
|
||||
- SIG Instrumentation / Structured Logging WG lead
|
||||
- SIG Storage member
|
||||
- SIG Node contributor
|
||||
- SIG Scheduling contributor
|
||||
|
||||
## What I have done
|
||||
|
||||
I have been involved with Kubernetes since 2018. I’ve worked on a variety of
|
||||
topics covering several different SIGs. Enhancements that I have designed and
|
||||
implemented include:
|
||||
|
||||
- Generic Ephemeral Volumes (GA)
|
||||
- Storage Capacity Tracking (GA)
|
||||
- Contextual Logging (alpha)
|
||||
- Dynamic Resource Allocation (alpha)
|
||||
|
||||
As tech lead in SIG Testing for the E2E framework and working group lead for
|
||||
structured logging I am responsible for changes that affect all contributors of
|
||||
Kubernetes. I care about code quality and some of you might remember my
|
||||
initiative to enable [stricter pre-merge
|
||||
linting](https://groups.google.com/a/kubernetes.io/g/dev/c/myGiml72IbM/m/QdO5bgQiAQAJ)
|
||||
which is now active for all new PRs.
|
||||
|
||||
I am working with the maintainers of components that Kubernetes depends on
|
||||
(Ginkgo/Gomega, golangci-lint, forbidigo, and last but not least Go itself) to
|
||||
ensure that they meet the needs of Kubernetes.
|
||||
|
||||
## What I'll do
|
||||
|
||||
The conversion of logging to contextual, structured logging is an area where I
|
||||
have helped various new developers with their first contributions to
|
||||
Kubernetes. Finding and retaining new contributors is an on-going challenge. I
|
||||
intend to continue doing that also as member of the steering committee.
|
||||
|
||||
Kubernetes has been wildly successful. It is tempting to rest on those laurels
|
||||
and focus only on stabilizing the existing APIs. But that would ignore all the
|
||||
new ideas about how Kubernetes could also be used, lead to stagnation and push
|
||||
away the new developers who want to try out their ideas. Therefore I believe
|
||||
that Kubernetes needs to continue to evolve (of course with all the required
|
||||
care to not break existing users) and I hope to support that.
|
||||
|
||||
## Resources About Me
|
||||
|
||||
- Presentations and some of the more important blog posts:
|
||||
- 2019: [KubeCon China: E2E Testing: Real Developers Don't Test... But They Should](https://kccncosschn19eng.sched.com/event/NrmX/e2e-testing-real-developers-dont-test-but-they-should-patrick-ohly-intel)
|
||||
- 2020: [KubeCon NA: Persistent Memory in Kubernetes](https://kccncna20.sched.com/event/ekFE/persistent-memory-in-kubernetes-patrick-ohly-intel)
|
||||
- 2022: [Contextual Logging blog post](https://www.kubernetes.dev/blog/2022/05/25/contextual-logging/)
|
||||
- 2023: [KubeCon EU: Keeping the Lights on and the Bugs Away](https://kccnceu2023.sched.com/event/1Hzcr/keeping-the-lights-on-and-the-bugs-away-patrick-ohly-intel), [E2E testing best practices reloaded](https://www.kubernetes.dev/blog/2023/04/12/e2e-testing-best-practices-reloaded/)
|
||||
|
||||
- Awards for work on Kubernetes:
|
||||
- 2021: [SIG Instrumentation](https://www.kubernetes.dev/community/awards/2021/)
|
||||
- 2022: [SIG Instrumentation, Architecture and Testing](https://www.kubernetes.dev/community/awards/2022/), [CNCF Chop Wood & Carry Water](https://github.com/cncf/awards#2022-chop-wood-carry-water)
|
||||
- 2023: [Google Open Source Peer Award](https://opensource.googleblog.com/2023/05/google-open-source-peer-bonus-program-announces-first-group-of-winners-2023.html)
|
||||
|
||||
- Links to social media
|
||||
- LinkedIn: [Patrick Ohly](https://www.linkedin.com/in/patrickohly/)
|
||||
|
|
@ -0,0 +1,48 @@
|
|||
-------------------------------------------------------------
|
||||
name: Noah Abrahams
|
||||
ID: qedrakmar
|
||||
info:
|
||||
- employer: Oracle
|
||||
- slack: nabrahams
|
||||
-------------------------------------------------------------
|
||||
|
||||
## SIGs and WGs
|
||||
|
||||
- SIG Contributor Experience (Non-Code Contributor Initiative Lead)
|
||||
- SIG Release (1.10 Release Team)
|
||||
- SIG PM (archived)
|
||||
- WG LTS
|
||||
|
||||
## What I have done
|
||||
|
||||
I got started with Kubernetes in 2016, and have been devoted to the project and ecosystem since then.
|
||||
|
||||
Some notable line items:
|
||||
|
||||
- Created and Lead the Non-Code Contributors initiative working within the Contributor Documentation subproject and with TAG Contributor Strategy
|
||||
- Ran Contributor Summits all over the world, from Day-of Operations starting with Seattle in 2018 to serving as Lead for Amsterdam in 2023
|
||||
- Worked as part of the Kubecon Program Committee in North America, Europe, and Asia, including as a Track Chair
|
||||
- Helped onboard new contributors through previous New Contributors Workshops
|
||||
- Onboarded new community members through group mentoring at Kubecon
|
||||
- Spoke at and ran meetups, including creating and running the Las Vegas meetup
|
||||
- Helped with the early formation of the first WG-LTS, and trying to represent the unrepresented in the reformed WG.
|
||||
- Improved our Release Notes process as part of Release Team
|
||||
|
||||
As a contributor, my primary rallying cry has been around non-code contributions, and I continue to lean into expanding our contributor base in this direction. As stated elsewhere, I focus on behind-the-scenes work that makes your job and your life easier. I’ve also been a CNCF Ambassador for many years, and stepped in anywhere else that I can help people get better and become more involved.
|
||||
|
||||
## What I'll do
|
||||
|
||||
I understand that Steering is a human-centered governance role, and is not a technical role, so I will serve while constantly keeping in mind our priorities of People first, Project second, Company third. I intend to give attention to all the people in our communities, but especially approvers and maintainers who are generally facing burnout and need help.
|
||||
|
||||
Related to that, I want to put focus on inclusion and accessibility, to make sure that all our people feel safe and enabled to contribute, regardless of race, gender, orientation, geographical location, or anything else, so more of them can be promoted up the contributor ladder. Underrepresented geographies are of particular interest to me here, and I would like to work on enabling our people in those regions, as well as examining what that means in terms of distributing work load between our SIG chairs and TLs, and our various admins in general. I also intend to join in on the efforts to review and potentially revamp the process around our annual reports, to both increase value to and decrease the cognitive load on the various SIGs.
|
||||
|
||||
Above all other projects and endeavors, I will be a steward, a resource, a liaison, and a friend, providing for the health and well-being of this community through governance, helping every one of the people whose lives it touches, so this project can continue to grow and thrive. I will encourage and help you, because you deserve to succeed, and when you succeed we all benefit.
|
||||
|
||||
## Resources About Me
|
||||
|
||||
- Some Talks By Me
|
||||
- [Opening the Contributor Summit in Amsterdam, 2023](https://www.youtube.com/watch?v=dL7cYhzAFrE&list=PL69nYSiGNLP06HYgwMWJJZmJHreLCrd21)
|
||||
- My fun Kubecon LA Talk: [A Safari of Kubernetes and its Natural Habitat](https://www.youtube.com/watch?v=RnhRj_EsYtk)
|
||||
- [A talk about communication at a New Contributor Workshop, 2018](https://www.youtube.com/watch?v=AVoat-IdCGA)
|
||||
- My Mastodon: [@nabrahams@hachyderm.io](https://hachyderm.io/@nabrahams)
|
||||
|
||||
|
|
@ -0,0 +1,90 @@
|
|||
-------------------------------------------------------------
|
||||
name: Maciej Szulik
|
||||
ID: soltysh
|
||||
info:
|
||||
- employer: Red Hat
|
||||
- slack: soltysh
|
||||
-------------------------------------------------------------
|
||||
|
||||
## SIGS
|
||||
|
||||
- SIG Apps chair and technical lead
|
||||
- SIG API Machinery member
|
||||
- SIG CLI technical lead
|
||||
- WG Batch organizer
|
||||
|
||||
## What I have done
|
||||
|
||||
I've been an active Kubernetes contributor since late 2014. The majority of my
|
||||
contributions can be divided between the SIGs and Work Groups mentioned above.
|
||||
|
||||
My kubectl contributions have been recognized, and in 2018, I joined SIG CLI
|
||||
leadership. Over the past 5 years, I've managed to grow SIG CLI into a lively,
|
||||
welcoming and open group. I've helped grow new leaders who could smoothly take
|
||||
over roles from longtime predecessors. In early 2022, I was able to comfortably
|
||||
step down from my chair role allowing those others to successfully lead the SIG.
|
||||
During my tenure, I've been able to drive several major refactoring efforts
|
||||
inside Kubectl, either as the primary developer, reviewer or mentor. These
|
||||
include: [moving kubectl to staging](https://github.com/kubernetes/enhancements/issues/1020),
|
||||
extracting [helpers for creating kubectl-like commands](https://github.com/kubernetes/cli-runtime),
|
||||
and standardizing the shape of every command.
|
||||
I'm still helping SIG CLI with technical oversight, advising on several of those
|
||||
ongoing efforts, but I'm confident that we already have great leaders who can
|
||||
replace me in the near future.
|
||||
|
||||
In early 2021, I joined SIG Apps leadership, as a recognition for my long-time
|
||||
contributions to Kubernetes controllers (author of [Jobs](https://github.com/kubernetes/design-proposals-archive/blob/main/apps/job.md)
|
||||
and [CronJobs née ScheduledJobs](https://github.com/kubernetes/design-proposals-archive/blob/main/apps/cronjob.md)).
|
||||
Those 2 years have been a wild ride pushing [controllers to GA](https://github.com/kubernetes/enhancements/issues/19),
|
||||
improving workload stability ([MaxSurge for DaemonSet](https://github.com/kubernetes/enhancements/issues/1591),
|
||||
[MaxUnavailable for StatefulSet](https://github.com/kubernetes/enhancements/issues/961)),
|
||||
or trying to [consolidate controller statuses](https://github.com/kubernetes/enhancements/issues/2804).
|
||||
|
||||
Together with SIG Autoscaling, SIG Node and SIG Scheduling toward the end of
|
||||
2021, I helped co-organize Batch Work Group, where I'm continuously helping
|
||||
extend batch workloads ([Tracking jobs without lingering pods](https://github.com/kubernetes/enhancements/issues/2307),
|
||||
[Index Jobs](https://github.com/kubernetes/enhancements/issues/2624)) to be easier to run on Kubernetes.
|
||||
|
||||
Being an early contributor to the Kubernetes project allowed me to touch several
|
||||
areas beyond the ones mentioned above. Over the years, I wrote [first version of audit](https://github.com/kubernetes/kubernetes/pull/27087),
|
||||
and then helped shape [the current mechanism](https://github.com/kubernetes/enhancements/issues/22).
|
||||
In addition, I have various contributions in the broad API server, which
|
||||
interested readers can verify browsing through [git history](https://github.com/kubernetes/kubernetes/commits?author=soltysh)
|
||||
;-)
|
||||
|
||||
Last but not least, in 2022, with the help from SIG Contribex, I've managed to
|
||||
organize mentoring cohorts for both of the [SIGs Apps and CLI](https://github.com/kubernetes/community/issues/6665).
|
||||
Growing the ranks of reviewers and approvers for these groups continues to be
|
||||
one of my top priorities for the longevity of the entire project.
|
||||
|
||||
## What I'll do
|
||||
|
||||
Maintaining a healthy group of people capable of working on the project on a
|
||||
daily basis continues to be one of my highest priorities. I'm hoping that being
|
||||
part of the Steering Committee will allow me to push that goal further. I'm
|
||||
already working together with SIG Contribex on improving the mentoring cohorts
|
||||
for the next rounds and working to make it easier to run by the leads while also
|
||||
being more welcoming for new contributors.
|
||||
|
||||
In parallel with growing next generations of contributors, the stability of the
|
||||
project as seen by end users is paramount. I'd like to ensure that efforts like
|
||||
Production Readiness continue to be the centerpiece of everyone's mind.
|
||||
|
||||
Lastly, I'm just a regular person with a lifetime passion for software
|
||||
engineering, and just like every one of us, I also make mistakes. That's why I
|
||||
would like to ask you, dear reader, to keep me honest and reach out to me
|
||||
whenever I will not be able to uphold the above standards. I know that my avatar
|
||||
both on github and slack looks scary, but trust me I am not. Please feel free
|
||||
to ping me when you need me :-)
|
||||
|
||||
## Resources About Me
|
||||
|
||||
- Twitter: [@soltysh](https://twitter.com/soltysh)
|
||||
- LinkedIn: [Maciej Szulik](https://www.linkedin.com/in/maciejszulik/)
|
||||
- Talks:
|
||||
- [Writing Controllers for Everyone](https://www.youtube.com/watch?v=AUNPLQVxvmw)
|
||||
- [The Long, Winding and Bumpy Road to CronJob’s GA](https://www.youtube.com/watch?v=o5h6s3A9bXY&pp=ygUNbWFjaWVqIHN6dWxpaw%3D%3D)
|
||||
- [Audit in Kubernetes, the Future is Here](https://www.youtube.com/watch?v=Up1qgVIzoVM&pp=ygUNbWFjaWVqIHN6dWxpaw%3D%3D)
|
||||
- [Kubectl code tour](https://youtu.be/eZeCFRh2uGg?t=540)
|
||||
- [The Cube interview](https://www.youtube.com/watch?v=iWnNFUrqZdM)
|
||||
|
||||
|
|
@ -0,0 +1,54 @@
|
|||
-------------------------------------------------------------
|
||||
name: Marko Mudrinić
|
||||
ID: xmudrii
|
||||
info:
|
||||
- employer: Kubermatic
|
||||
- slack: xmudrii
|
||||
-------------------------------------------------------------
|
||||
|
||||
## SIGS
|
||||
|
||||
- SIG Release
|
||||
- 2020-present: Release Manager
|
||||
- 2019-2020: Release Manager Associate
|
||||
- 2018-2019: Bug Triage Lead (v1.16), Bug Triage Shadow (v1.14-v1.15)
|
||||
- SIG K8s Infra
|
||||
- Contributor and SIG member
|
||||
- Co-creator and maintainer of EKS-based Prow build cluster
|
||||
|
||||
## What I have done
|
||||
|
||||
I started contributing to the Kubernetes project in 2018 as a Google Summer of Code (GSoC) student working on [Etcd Proxy for Aggregated API servers](https://github.com/xmudrii/etcdproxy-controller). After my GSoC internship, I contributed to SIG Cluster Lifecycle, mainly to the Cluster API project. I created [Cluster API Provider for DigitalOcean](https://github.com/kubernetes-sigs/cluster-api-provider-digitalocean) and continued maintaining it until early 2021.
|
||||
|
||||
In the meantime, I've been contributing to SIG Release. Initially, I was part of the Release Team for three release cycles: v1.14 and v1.15 as a Bug Triage Shadow, and v1.16 as a Bug Triage Lead. I've been selected to join the Release Engineering team as a Release Manager Associate in late 2019, where I worked on improving processes and documentation related to cutting and maintaining releases.
|
||||
|
||||
In 2020, I've been promoted to a fully-fledged Release Manager. My duties as a Release Manager include cutting releases, ensuring stability and reliability of release branches, maintaining tooling used by Kubernetes and other projects in the ecosystem to cut and facilitate releases in a reliable and secure way, and more.
|
||||
|
||||
One of my most notable contributions include designing and implementing [Kubernetes community-owned package repositories which went live in August 2023](https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/). Migrating to community-owned repositories was one of the longest standing problems in SIG Release and the Kubernetes community, dating back to 2019. I was recognized for my outstanding contributions to SIG Release in 2022 with a [Kubernetes Contributor Award](https://www.kubernetes.dev/community/awards/2022/#release).
|
||||
|
||||
As of beginning of 2023, I joined SIG K8s Infra efforts to reduce GCP spendings by creating and maintaining a EKS-based Prow build cluster. I co-lead efforts to migrate relevant jobs from the Google infrastructure to the new EKS-based Prow build cluster.
|
||||
|
||||
I'm going to be a mentor in the upcoming LFX Term 3: Sept-Nov for [the Kubernetes project](https://mentorship.lfx.linuxfoundation.org/project/47f53d22-ff5c-4479-b701-3ca3dbc7df0a). As of February 2023, I'm an Undergraduate Teaching Assistant at School of Computing, University Union, Belgrade, mainly teaching Kubernetes and Cloud Native technologies to final year students.
|
||||
|
||||
## What I'll do
|
||||
|
||||
Having begun my Kubernetes journey as a student and ascending to the Release Manager position in SIG Release, I've witnessed numerous challenges. Beyond making initial contributions as seamless as possible, I'm committed to cultivating long-term, sustainable contributions within the community. Steering plays a key role in upholding the community values, and ensuring project's health and long-term sustainability.
|
||||
|
||||
Kubernetes project in large depends on contributions from people working on the project as volunteers in their free time. It's important to recognize this and foster sustainable and diverse contributor base. I want to bring my perspective as someone who have worn many different hats over the past 5 years: being a full-time student, Release Manager, mentor, and a teaching assistant. This includes:
|
||||
|
||||
- Helping SIGs build diverse and sustainable contributor base through different opportunities (mentoring cohorts and similar initiatives)
|
||||
- Encouraging SIGs to build a contributor ladder enabling contributors to climb to reviewer/approver roles and provide more value to the community
|
||||
- Providing guidance to SIGs on how to be more appealing to contributors from EMEA and APAC regions who are facing many challenges especially due to timezone differences
|
||||
- Making Kubernetes more attractive to contributors from the academia backgrounds (including students and faculty staff)
|
||||
- Embracing asynchronous over synchronous communications as a way to make contributing to the project more welcoming
|
||||
- Upholding the community values and identifying potential improvement areas in the community and project
|
||||
|
||||
## Resources About Me
|
||||
|
||||
- Twitter: [@xmudrii](https://twitter.com/xmudrii)
|
||||
- LinkedIn: [@xmudrii](https://linkedin.com/in/xmudrii/)
|
||||
- Talks
|
||||
- [KubeCon EU 2023: How SIG Release Makes Kubernetes Releases Even More Stable & Secure - Veronica Lopez & Marko Mudrinić](https://youtu.be/AP9G5Jtn9y4)
|
||||
- [Contributor Summit EU 2023: Migrating Kubernetes CI Jobs to AWS - Marko Mudrinić & Patryk Przekwas](https://youtu.be/xEADvrgi1ek)
|
||||
- [KubeCon NA 2018: Lightning Talk: Spawning Kubernetes In CI For Integration Tests - Marko Mudrinić](https://youtu.be/ZiJn7olAS1M)
|
||||
- My other talks can be found in the following [YouTube playlist](https://youtube.com/playlist?list=PLvNBqHHXyMOBufmiuBrIQvtgOp3smF1Jx&si=VgyVGNO4HVFa6d16)
|
||||
|
|
@ -0,0 +1,26 @@
|
|||
# Results of the 2023 Steering Committee Election
|
||||
|
||||
- Number of seats open: 4 (2 year term)
|
||||
- Number of eligible voters: 712
|
||||
- Number of votes cast: 209
|
||||
- Turnout: 29.35%
|
||||
|
||||
## Winners
|
||||
|
||||
The winners of the open seats are as follows for their two year term:
|
||||
|
||||
1. [Maciej Szulik](https://github.com/soltysh)
|
||||
2. [Patrick Ohly](https://github.com/pohly)
|
||||
3. [Paco Xu 徐俊杰](https://github.com/pacoxu)
|
||||
4. [Stephen Augustus](https://github.com/justaugustus)
|
||||
|
||||
The rest of the candidates were placed as follows:
|
||||
5. [Natali Vlatko](https://github.com/natalisucks)
|
||||
6. [Arnaud Meukam](https://github.com/ameukam)
|
||||
7. [Divya Mohan](https://github.com/divya-mohan0209)
|
||||
8. [Marko Mudrinić](https://github.com/xmudrii)
|
||||
9. [Vince Prignano](https://github.com/vincepri)
|
||||
10. [Jason DeTiberus](https://github.com/detiber)
|
||||
11. [Noah Abrahams](https://github.com/qedrakmar)
|
||||
|
||||
Proportional representation limits were not invoked for this election.
|
||||
|
|
@ -8,10 +8,6 @@
|
|||
# below, please fill out an exception request and the elections team will get back to
|
||||
# you as quickly as possible: https://elections.k8s.io/app/elections/steering---2023/exception
|
||||
#
|
||||
# History:
|
||||
# Log of changes to the file
|
||||
# 2023-08-07 - Initial setup with voters from devstats+org, plus CCoC + SRC
|
||||
#
|
||||
eligible_voters:
|
||||
- '249043822'
|
||||
- 196Ikuchil
|
||||
|
|
@ -213,6 +209,7 @@ eligible_voters:
|
|||
- fsmunoz
|
||||
- furkatgofurov7
|
||||
- fuxiuyin
|
||||
- fykaa
|
||||
- g-gaston
|
||||
- Garima-Negi
|
||||
- Garrybest
|
||||
|
|
@ -277,6 +274,7 @@ eligible_voters:
|
|||
- jberkus
|
||||
- jbpratt
|
||||
- jcjesus
|
||||
- jeefy
|
||||
- Jefftree
|
||||
- jeremyrickard
|
||||
- jhrozek
|
||||
|
|
@ -327,6 +325,7 @@ eligible_voters:
|
|||
- kbhawkey
|
||||
- kcmartin
|
||||
- keithmattix
|
||||
- kendallnelson
|
||||
- kerthcet
|
||||
- kevindelgado
|
||||
- kflynn
|
||||
|
|
@ -351,6 +350,7 @@ eligible_voters:
|
|||
- krol3
|
||||
- kundan2707
|
||||
- kwiesmueller
|
||||
- lachie83
|
||||
- landreasyan
|
||||
- lauchokyip
|
||||
- lauralorenz
|
||||
|
|
@ -462,6 +462,7 @@ eligible_voters:
|
|||
- nikhita
|
||||
- nilekhc
|
||||
- nilo19
|
||||
- nitishfy
|
||||
- niuzhenguo
|
||||
- nixpanic
|
||||
- njuettner
|
||||
|
|
@ -483,6 +484,7 @@ eligible_voters:
|
|||
- pacoxu
|
||||
- palnabarun
|
||||
- panslava
|
||||
- parispittman
|
||||
- pawbana
|
||||
- pbetkier
|
||||
- perriea
|
||||
|
|
@ -491,6 +493,7 @@ eligible_voters:
|
|||
- PiotrProkop
|
||||
- pjbgf
|
||||
- pkprzekwas
|
||||
- pnbrown
|
||||
- pohly
|
||||
- Pradumnasaraf
|
||||
- Prajyot-Parab
|
||||
|
|
@ -559,6 +562,7 @@ eligible_voters:
|
|||
- sashrith
|
||||
- SataQiu
|
||||
- sathyanarays
|
||||
- savitharaghunathan
|
||||
- sayantani11
|
||||
- sbangari
|
||||
- sbueringer
|
||||
|
|
@ -595,7 +599,7 @@ eligible_voters:
|
|||
- spencerhance
|
||||
- spiffxp
|
||||
- spowelljr
|
||||
- sraghunathan
|
||||
- sreeram-venkitesh
|
||||
- srm09
|
||||
- starpit
|
||||
- stevehipwell
|
||||
|
|
|
|||
|
|
@ -1,7 +1,9 @@
|
|||
## RENAME THIS FILE TO election.yaml
|
||||
name: {{YEAR}} Steering Committee Election
|
||||
organization: Kubernetes
|
||||
# Start of day in UTC for opening: 2023-08-29 00:00:01
|
||||
start_datetime: {{DATETIME VOTING STARTS IN UTC}}
|
||||
# End of day Anywhere on Earth for closing. Write 2023-09-26 as: 2023-09-27 11:59:59
|
||||
end_datetime: {{DATETIME VOTING ENDS IN UTC}}
|
||||
no_winners: {{# BEING ELECTED}}
|
||||
allow_no_opinion: True
|
||||
|
|
@ -15,4 +17,5 @@ election_officers:
|
|||
- {{EO 3}}
|
||||
eligibility: Kubernetes Org members with {{NUM}} or more contributions in the last year can vote. See [the election guide](https://github.com/kubernetes/community/tree/master/elections/steering/{{YEAR}})
|
||||
exception_description: Not all contributions are measured by DevStats. If you have contributions that are not so measured, then please request an exception to allow you to vote via the Elekto application.
|
||||
# End of day Anywhere on Earth for closing. Write 2023-09-23 as: 2023-09-24 11:59:59
|
||||
exception_due: {{DATETIME 3-4 DAYS BEFORE VOTING ENDS}}
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ By Special Interest Group (SIG)
|
|||
|
||||
#### Scheduling
|
||||
|
||||
- Huang Wei
|
||||
- Wei Huang
|
||||
|
||||
#### Storage
|
||||
|
||||
|
|
@ -32,4 +32,4 @@ By Special Interest Group (SIG)
|
|||
|
||||
#### WG Multitenancy
|
||||
|
||||
- Ryan Bezdicek
|
||||
- Ryan Bezdicek
|
||||
|
|
|
|||
|
|
@ -230,6 +230,7 @@ type Subproject struct {
|
|||
Description string `yaml:",omitempty"`
|
||||
Contact *Contact `yaml:",omitempty"`
|
||||
Owners []string
|
||||
Leads []Person `yaml:",omitempty"`
|
||||
Meetings []Meeting `yaml:",omitempty"`
|
||||
}
|
||||
|
||||
|
|
@ -395,6 +396,9 @@ func (c *Context) Sort() {
|
|||
return subproject.Contact.GithubTeams[i].Name < subproject.Contact.GithubTeams[j].Name
|
||||
})
|
||||
}
|
||||
sort.Slice(subproject.Leads, func(i, j int) bool {
|
||||
return subproject.Leads[i].GitHub < subproject.Leads[j].GitHub
|
||||
})
|
||||
sort.Strings(subproject.Owners)
|
||||
sort.Slice(subproject.Meetings, func(i, j int) bool {
|
||||
return subproject.Meetings[i].Description < subproject.Meetings[j].Description
|
||||
|
|
|
|||
|
|
@ -32,6 +32,14 @@ The [charter]({{.CharterLink}}) defines the scope and governance of the {{.Name}
|
|||
* {{.Name}} (**[@{{.GitHub}}](https://github.com/{{.GitHub}})**){{if .Company}}, {{.Company}}{{end}}
|
||||
{{- end }}
|
||||
{{- end }}
|
||||
|
||||
{{- if .Leadership.EmeritusLeads }}
|
||||
|
||||
## Emeritus Members
|
||||
{{ range .Leadership.EmeritusLeads }}
|
||||
* {{.Name}} (**[@{{.GitHub}}](https://github.com/{{.GitHub}})**)
|
||||
{{- end }}
|
||||
{{- end }}
|
||||
{{- end }}
|
||||
|
||||
## Contact
|
||||
|
|
@ -82,7 +90,7 @@ The following [subprojects][subproject-definition] are owned by the {{.Name}} Co
|
|||
- [Mailing List]({{.Contact.MailingList}})
|
||||
{{- end }}
|
||||
{{- if .Contact.GithubTeams }}
|
||||
- GitHub Teams:
|
||||
- GitHub Teams:
|
||||
{{- range .Contact.GithubTeams }}
|
||||
- [@kubernetes/{{.Name}}](https://github.com/orgs/kubernetes/teams/{{.Name}}) {{- if .Description }} - {{.Description}}{{- end}}
|
||||
{{- end }}
|
||||
|
|
|
|||
|
|
@ -89,6 +89,12 @@ The following [subprojects][subproject-definition] are owned by sig-{{.Label}}:
|
|||
### {{.Name}}
|
||||
{{- if .Description }}
|
||||
{{ trimSpace .Description }}
|
||||
{{- end }}
|
||||
{{- if .Leads }}
|
||||
- **Leads:**{{ range .Leads }}
|
||||
- {{.Name}} (**[@{{.GitHub}}](https://github.com/{{.GitHub}})**){{if .Company}}, {{.Company}}{{end}}
|
||||
{{- end }}
|
||||
|
||||
{{- end }}
|
||||
- **Owners:**
|
||||
{{- range .Owners }}
|
||||
|
|
|
|||
|
|
@ -56,7 +56,9 @@ GitHub organization.
|
|||
They also have approval privileges for adding new members to the GitHub config.
|
||||
|
||||
Our current coordinators are:
|
||||
TBD
|
||||
* Ader Fu (**[ydFu](https://github.com/ydFu)**, Taipei Standard Time)
|
||||
* Heba Elayoty (**[helayoty](https://github.com/helayoty)**, Pacific Time)
|
||||
* Mario Jason Braganza (**[jasonbraganza](https://github.com/jasonbraganza)**, Indian Standard Time)
|
||||
|
||||
## Project Owned Organizations
|
||||
|
||||
|
|
|
|||
|
|
@ -97,8 +97,10 @@ Corporate CLA](https://github.com/cncf/cla/blob/master/corporate-cla.pdf)
|
|||
* If (a) contributor(s) have not signed the CLA and could not be reached, a
|
||||
NOTICE file should be added referencing section 7 of the CLA with a list of
|
||||
the developers who could not be reached
|
||||
* Licenses of dependencies are acceptable; project owners can ping
|
||||
[@caniszczyk](https://github.com/caniszczyk) for review of third party deps
|
||||
* Licenses of dependencies are acceptable; please review the [allowed-third-party-license-policy.md](https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md)
|
||||
and [exceptions](https://github.com/cncf/foundation/tree/main/license-exceptions).
|
||||
If your dependencies are not covered, then please open a `License Exception Request` issue in
|
||||
[cncf/foundation](https://github.com/cncf/foundation/issues) repository.
|
||||
* Boilerplate text across all files should attribute copyright as follows:
|
||||
`"Copyright <Project Authors>"` if no CLA was in place prior to donation
|
||||
* Additions of [the standard Kubernetes header](https://git.k8s.io/kubernetes/hack/boilerplate/boilerplate.go.txt)
|
||||
|
|
|
|||
|
|
@ -3,8 +3,7 @@ contributors/guide/contributor-cheatsheet/README-fr.md
|
|||
contributors/guide/contributor-cheatsheet/README-it.md
|
||||
contributors/guide/contributor-cheatsheet/README-pt.md
|
||||
committee-steering/meeting-notes-archive
|
||||
elections/steering/2022/voters.yaml
|
||||
elections/steering/2023/voters.yaml
|
||||
elections/steering/.*/voters.yaml
|
||||
events/2014
|
||||
events/elections/2017/
|
||||
sig-contributor-experience/meeting-notes-archive
|
||||
|
|
|
|||
33
liaisons.md
33
liaisons.md
|
|
@ -33,34 +33,35 @@ members will assume one of the departing members groups.
|
|||
| [SIG API Machinery](sig-api-machinery/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) |
|
||||
| [SIG Apps](sig-apps/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) |
|
||||
| [SIG Architecture](sig-architecture/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
|
||||
| [SIG Auth](sig-auth/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) |
|
||||
| [SIG Autoscaling](sig-autoscaling/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) |
|
||||
| [SIG CLI](sig-cli/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||||
| [SIG Cloud Provider](sig-cloud-provider/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||||
| [SIG Auth](sig-auth/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
|
||||
| [SIG Autoscaling](sig-autoscaling/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
|
||||
| [SIG CLI](sig-cli/README.md) | Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**) |
|
||||
| [SIG Cloud Provider](sig-cloud-provider/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
|
||||
| [SIG Cluster Lifecycle](sig-cluster-lifecycle/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) |
|
||||
| [SIG Contributor Experience](sig-contributor-experience/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) |
|
||||
| [SIG Docs](sig-docs/README.md) | Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) |
|
||||
| [SIG Instrumentation](sig-instrumentation/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) |
|
||||
| [SIG Docs](sig-docs/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||||
| [SIG etcd](sig-etcd/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) |
|
||||
| [SIG Instrumentation](sig-instrumentation/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
|
||||
| [SIG K8s Infra](sig-k8s-infra/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||||
| [SIG Multicluster](sig-multicluster/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) |
|
||||
| [SIG Network](sig-network/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) |
|
||||
| [SIG Node](sig-node/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) |
|
||||
| [SIG Network](sig-network/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
|
||||
| [SIG Node](sig-node/README.md) | Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**) |
|
||||
| [SIG Release](sig-release/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) |
|
||||
| [SIG Scalability](sig-scalability/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) |
|
||||
| [SIG Scheduling](sig-scheduling/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
|
||||
| [SIG Security](sig-security/README.md) | Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) |
|
||||
| [SIG Storage](sig-storage/README.md) | Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) |
|
||||
| [SIG Testing](sig-testing/README.md) | Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) |
|
||||
| [SIG UI](sig-ui/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||||
| [SIG Security](sig-security/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||||
| [SIG Storage](sig-storage/README.md) | Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**) |
|
||||
| [SIG Testing](sig-testing/README.md) | Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**) |
|
||||
| [SIG UI](sig-ui/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
|
||||
| [SIG Windows](sig-windows/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
|
||||
| [WG API Expression](wg-api-expression/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
|
||||
| [WG Batch](wg-batch/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) |
|
||||
| [WG Data Protection](wg-data-protection/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) |
|
||||
| [WG IoT Edge](wg-iot-edge/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) |
|
||||
| [WG Data Protection](wg-data-protection/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
|
||||
| [WG IoT Edge](wg-iot-edge/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
|
||||
| [WG LTS](wg-lts/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) |
|
||||
| [WG Policy](wg-policy/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) |
|
||||
| [WG Policy](wg-policy/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
|
||||
| [WG Structured Logging](wg-structured-logging/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) |
|
||||
| [Committee Code of Conduct](committee-code-of-conduct/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) |
|
||||
| [Committee Code of Conduct](committee-code-of-conduct/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) |
|
||||
| [Committee Security Response](committee-security-response/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||||
<!-- BEGIN CUSTOM CONTENT -->
|
||||
## Expectations
|
||||
|
|
|
|||
|
|
@ -14,8 +14,9 @@ The [charter](charter.md) defines the scope and governance of the API Machinery
|
|||
|
||||
## Meetings
|
||||
*Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-api-machinery) for the group will typically add invites for the following meetings to your calendar.*
|
||||
* Kubebuilder and Controller Runtime Meeting: [Thursdays at 11:00 PT (Pacific Time)]() (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=11:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1Ih-2cgg1bUrLwLVTB9tADlPcVdgnuMNBGbUl4D-0TIk/edit?usp=sharing).
|
||||
* Kubebuilder Meeting: [Thursdays at 11:00 PT (Pacific Time)]() (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=11:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1GbSkHAxIaFTm2fL92z3WeWrCtnIjXfr7gNZSySLHhmk/edit?usp=sharing).
|
||||
* [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP0SOaFeA9f3dwdCNECEKkX3).
|
||||
* Regular SIG Meeting: [Wednesdays at 11:00 PT (Pacific Time)](https://zoom.us/my/apimachinery) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=11:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://goo.gl/0lbiM9).
|
||||
* [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP21oW3hbLyjjj4XhrwKxH2R).
|
||||
|
|
|
|||
|
|
@ -46,14 +46,14 @@ David Eads, Daniel Smith, Federico Bongiovanni
|
|||
|
||||
3. Same question as above but for working groups.
|
||||
[wg-api-expression](https://github.com/kubernetes/community/blob/master/wg-api-expression/README.md) has its own
|
||||
regular meeting cadence and did its own [annual report](https://github.com/kubernetes/community/blob/master/wg-api-expression/2020-annual-report.md).
|
||||
regular meeting cadence and did its own [annual report](https://github.com/kubernetes/community/blob/master/wg-api-expression/annual-report-2020.md).
|
||||
|
||||
[wg-component-standard](https://github.com/kubernetes/community/blob/master/wg-component-standard/README.md) has its own
|
||||
[wg-component-standard](https://github.com/kubernetes/community/blob/master/archive/wg-component-standard/README.md) has its own
|
||||
regular meeting cadence.
|
||||
The working group is not as active as it once was, see the [mailing list thread](https://groups.google.com/g/kubernetes-dev/c/sQGrk6HWyj0).
|
||||
|
||||
[wg-multitenancy](https://github.com/kubernetes/community/tree/master/wg-multitenancy) has its own regular meeting cadence
|
||||
and did its own [annual report](https://github.com/kubernetes/community/blob/master/wg-multitenancy/2021-annual-report.md).
|
||||
and did its own [annual report](https://github.com/kubernetes/community/blob/master/wg-multitenancy/annual-report-2020.md).
|
||||
|
||||
4. When was your last public community-wide update? (provide link to deck and/or recording)
|
||||
[May 2020](https://docs.google.com/presentation/d/1UWRaMVtTD3yVhJ3MGBpt7LRIaRHTaQZoGlDT7Bl7jLE/edit#slide=id.g401c104a3c_0_0)
|
||||
|
|
@ -100,7 +100,7 @@ David Eads, Daniel Smith, Federico Bongiovanni
|
|||
|
||||
Currently underway:
|
||||
1. [server-side-apply](https://github.com/kubernetes/enhancements/issues/555) to GA
|
||||
2. [server-side-apply client](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2144-clientgo-apply#alternative-1-generated-structs-where-all-fields-are-pointers)
|
||||
2. [server-side-apply client](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2155-clientgo-apply#alternative-generated-structs-where-all-fields-are-pointers)
|
||||
3. [optionally skip backend TLS verifiction](https://github.com/kubernetes/enhancements/issues/1295)
|
||||
4. [namespace labels](https://github.com/kubernetes/enhancements/pull/2162)
|
||||
5. Getting ready for CRD and admission webhook v1beta1 API removal: [reminder on kubernetes-dev](https://groups.google.com/g/kubernetes-dev/c/z_AE1EHhZF4/m/kBd3HkWxAwAJ).
|
||||
|
|
|
|||
|
|
@ -159,7 +159,7 @@ The following [subprojects][subproject-definition] are owned by sig-api-machiner
|
|||
- [kubernetes/kubernetes/cmd/kube-apiserver](https://github.com/kubernetes/kubernetes/blob/master/cmd/kube-apiserver/OWNERS)
|
||||
- [kubernetes/kubernetes/cmd/kube-controller-manager](https://github.com/kubernetes/kubernetes/blob/master/cmd/kube-controller-manager/OWNERS)
|
||||
- [kubernetes/kubernetes/pkg/kubeapiserver](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubeapiserver/OWNERS)
|
||||
- [kubernetes/kubernetes/pkg/master](https://github.com/kubernetes/kubernetes/blob/master/pkg/master/OWNERS)
|
||||
- [kubernetes/kubernetes/pkg/master](https://github.com/kubernetes/kubernetes/blob/master/pkg/OWNERS)
|
||||
- [kubernetes/kubernetes/staging/src/k8s.io/controller-manager](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/controller-manager/OWNERS)
|
||||
### server-crd
|
||||
- **Owners:**
|
||||
|
|
|
|||
Binary file not shown.
|
|
@ -36,7 +36,7 @@ The [charter](charter.md) defines the scope and governance of the Architecture S
|
|||
The Chairs of the SIG run operations and processes governing the SIG.
|
||||
|
||||
* Derek Carr (**[@derekwaynecarr](https://github.com/derekwaynecarr)**), Red Hat
|
||||
* Davanum Srinivas (**[@dims](https://github.com/dims)**), Amazon Web Services
|
||||
* Davanum Srinivas (**[@dims](https://github.com/dims)**), Amazon
|
||||
* John Belamaric (**[@johnbelamaric](https://github.com/johnbelamaric)**), Google
|
||||
|
||||
## Contact
|
||||
|
|
@ -125,7 +125,7 @@ Establishing and documenting conventions for system and user-facing APIs, define
|
|||
* [API Review process](https://github.com/kubernetes/community/blob/master/sig-architecture/api-review-process.md)
|
||||
* [Deprecation policy](https://kubernetes.io/docs/reference/deprecation-policy/)
|
||||
|
||||
Please see the [API Reviews](https://github.com/orgs/kubernetes/projects/13) tracking board to follow the work of this sub-project. Please reach out to folks in the [OWNERS](https://git.k8s.io/design-proposals-archive/architecture/OWNERS) file if you are interested in joining this effort.
|
||||
Please see the [API Reviews](https://github.com/orgs/kubernetes/projects/169) tracking board to follow the work of this sub-project. Please reach out to folks in the [OWNERS](https://git.k8s.io/design-proposals-archive/architecture/OWNERS) file if you are interested in joining this effort.
|
||||
|
||||
## Enhancement Proposals
|
||||
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@
|
|||
|
||||
- For the enhancements subproject, all owners are all active.
|
||||
|
||||
- For the API review subproject, there are no standing meetings. The subproject coordinates via a [project board](https://github.com/orgs/kubernetes/projects/13) and [mailing list](https://groups.google.com/g/kubernetes-api-reviewers).
|
||||
- For the API review subproject, there are no standing meetings. The subproject coordinates via a [project board](https://github.com/orgs/kubernetes/projects/169) and [mailing list](https://groups.google.com/g/kubernetes-api-reviewers).
|
||||
|
||||
- For the code organization subproject, @dims and @liggitt run regular meetings and review PRs and issues, pulling in other owners as needed.
|
||||
|
||||
|
|
|
|||
|
|
@ -153,7 +153,7 @@ Continuing:
|
|||
- API guidance updates
|
||||
- [Object references](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#object-references), including cross-namespace references from namespaced objects
|
||||
- [Spec and Status](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status) ([#5842](https://github.com/kubernetes/community/pull/5842))
|
||||
- 114 [API reviews completed](https://github.com/orgs/kubernetes/projects/13) in 2021 (30 for v1.21, 45 for v1.22, 39 for v1.23)
|
||||
- 114 [API reviews completed](https://github.com/orgs/kubernetes/projects/169) in 2021 (30 for v1.21, 45 for v1.22, 39 for v1.23)
|
||||
- Each SIG can identify 2-3 people to be involved in API reviews - https://github.com/kubernetes/kubernetes/blob/v1.23.0/OWNERS_ALIASES#L451-L452
|
||||
- [Conformance Definition](https://github.com/kubernetes/community/tree/master/sig-architecture#conformance-definition-1)
|
||||
- We started 2021 with 128 endpoints remaining without conformance test.(69.13% conformance tested)
|
||||
|
|
|
|||
|
|
@ -78,14 +78,14 @@ Voluntary reviews apply towards non-core APIs that do not meet the [mandatory](#
|
|||
1. Request an API review for a PR or issue in the kubernetes org by adding the `api-review` label with a `/label api-review` comment (requests can be cancelled with a `/remove-label api-review` comment)
|
||||
* If this is a review of a PR implementing an already-reviewed design/KEP, reference the approved KEP and note any differences between the approved design and the implementation.
|
||||
|
||||
2. API reviews are tracked in a project board at https://github.com/orgs/kubernetes/projects/13
|
||||
2. API reviews are tracked in a project board at https://github.com/orgs/kubernetes/projects/169
|
||||
* Github query for requested reviews not yet in the project:
|
||||
* [`is:open org:kubernetes label:api-review -project:kubernetes/13`](https://github.com/search?q=is%3Aopen+org%3Akubernetes+label%3Aapi-review+-project%3Akubernetes%2F13)
|
||||
* [`is:open org:kubernetes label:api-review -project:kubernetes/169`](https://github.com/search?q=is%3Aopen+org%3Akubernetes+label%3Aapi-review+-project%3Akubernetes%2F169)
|
||||
* Github query for items in the project no longer requesting review:
|
||||
* [`is:open org:kubernetes -label:api-review project:kubernetes/13`](https://github.com/search?q=is%3Aopen+org%3Akubernetes+-label%3Aapi-review+project%3Akubernetes%2F13)
|
||||
* [`is:open org:kubernetes -label:api-review project:kubernetes/169`](https://github.com/search?q=is%3Aopen+org%3Akubernetes+-label%3Aapi-review+project%3Akubernetes%2F169)
|
||||
* Requests are triaged by API approvers/reviewers/moderators [regularly](#review-lifecycle-timing), and added to the project board if prereqs have been completed
|
||||
* As requests are added to the project board, that is reflected in the sidebar of the issue or PR, along with the current status (backlog, assigned, in progress, completed)
|
||||
* The API review backlog and queue is publicly visible at https://github.com/orgs/kubernetes/projects/13
|
||||
* The API review backlog and queue is publicly visible at https://github.com/orgs/kubernetes/projects/169
|
||||
|
||||
3. Backlog
|
||||
* An approver or moderator will adjust the prioritization of the issue in the backlog. Reviews are prioritized based on a number of factors:
|
||||
|
|
@ -99,14 +99,14 @@ Voluntary reviews apply towards non-core APIs that do not meet the [mandatory](#
|
|||
* An approver or moderator will assign an approver (or potentially aspiring reviewer - see *training reviews* below for the aspiring reviewer workflow)
|
||||
* Reviews are assigned based on reviewer capacity and domain knowledge
|
||||
* Assignment of reviewers is done on the issue/PR itself using the normal `/assign` method (works seamlessly with existing github/PR dashboard queries)
|
||||
* All API reviews assigned to an individual can be viewed in the project board ([example](https://github.com/orgs/kubernetes/projects/13/?card_filter_query=assignee%3Aliggitt)), for visibility on status, order, and reviewer load
|
||||
* All API reviews assigned to an individual can be viewed in the project board ([example](https://github.com/orgs/kubernetes/projects/169/views/3?filterQuery=assignee%3Aliggitt)), for visibility on status, order, and reviewer load
|
||||
|
||||
5. In Progress / Approved / Changes Requested / Rejected
|
||||
* Reviews proceed like a normal KEP or PR review. Possible outcomes:
|
||||
* Approval:
|
||||
* Implementation PRs are tagged with `/lgtm /approve` and merged normally
|
||||
* KEP PRs containing API designs can also be tagged with `/lgtm /approve`, but should explicitly note if API approval is being given. This approval should be linked to when later requesting review of the implementation PR, and should limit the scope of the implementation review to differences between the approved design and final implementation, problems encountered during implementation, and correctness of the implementation.
|
||||
* The approved issue is archived in the review project board, and the `api-review` label is removed.
|
||||
* The approved issue is archived in the review project board.
|
||||
* Changes requested:
|
||||
* Comments or questions are left on the PR or issue, and the reviewer notifies the submitter
|
||||
* The reviewer moves the issue to "Changes Requested" in the review project board
|
||||
|
|
|
|||
|
|
@ -37,13 +37,17 @@ KEP authors, and reviewed by the SIG leads. Once the leads are satisfied with
|
|||
both the overall KEP (i.e., it is ready to move to `implementable` state) and
|
||||
the PRR answers, the authors may request PRR approval:
|
||||
|
||||
* Make sure the Enhancement KEP is labeled `lead-opted-in` before PRR Freeze. This is required so that the Enhancements
|
||||
release team and PRR team are aware the KEP is targeting the release.
|
||||
* Assign a PRR approver from the `prod-readiness-approvers` list in the
|
||||
[OWNERS_ALIASES] file. This may be done earlier as well, to get early feedback
|
||||
or just to let the approver know. Reach out on the `#prod-readiness` Slack
|
||||
channel or just pick someone from the list. The team may rebalance the
|
||||
assignees if necessary.
|
||||
* Update the `kep.yaml`, setting the `stage`, `latest-milestone`, and the
|
||||
`milestone` struct (which captures per-stage release versions).
|
||||
`milestone` struct (which captures per-stage release versions). See the
|
||||
[KEP template](https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template)
|
||||
for required sections.
|
||||
* Create a `prod-readiness/<sig>/<KEP number>.yaml` file, with the PRR
|
||||
approver's GitHub handle for the specific stage
|
||||
* See this [example PRR approval request PR].
|
||||
|
|
@ -80,9 +84,28 @@ To become a reviewer:
|
|||
* Read/study previous PRR comments and production readiness responses in existing KEPs.
|
||||
* Choose some KEPs requiring PRR and perform a review. Put "shadow prod readiness review"
|
||||
in your review comments so that the assigned PRR approver knows your intent.
|
||||
* After at least one release cycle, if you have shown good judgement and quality reviews,
|
||||
you can propose yourself as approver by submitting a PRR to add your GitHub
|
||||
handle to the `prod-readiness-approvers` alias in [OWNERS_ALIASES].
|
||||
|
||||
### Becoming an approver
|
||||
|
||||
After serving as reviewer/shadow for at least one release and showing good judgement and quality reviews,
|
||||
you can propose yourself as an approver by submitting a PR to add your GitHub
|
||||
handle to the `prod-readiness-approvers` alias in [OWNERS_ALIASES].
|
||||
|
||||
When submitting the PR, you should include references to KEPs you reviewed that demonstrated a good variety
|
||||
of different situations.
|
||||
Here is a good starting point (remember that one PR can cover multiple categories):
|
||||
|
||||
* Transitions from new to alpha
|
||||
* Transitions from alpha to beta
|
||||
* Transitions from beta to GA
|
||||
* Must have successfully reviewed at least three enhancements that require coordination between multiple components.
|
||||
* Must have successfully reviewed at least three enhancements that require version skew consideration (both HA and component skew):
|
||||
does behavior fail safely and eventually reconcile.
|
||||
* Must have successfully reviewed at least three enhancements that are outside your primary domain.
|
||||
* Examples where the feature requires considering the case of administering thousands of clusters.
|
||||
This comes up frequently for host-based features in storage, node, or networking.
|
||||
* Examples where the feature requires considering the case of very large clusters. This is commonly covered by metrics.
|
||||
|
||||
|
||||
## Finding KEPs needing prod readiness review
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ The [charter](charter.md) defines the scope and governance of the Auth Special I
|
|||
* Regular SIG Meeting: [Wednesdays at 11:00 PT (Pacific Time)](https://zoom.us/j/264572674) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=11:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1woLGRoONE3EBVx-wTb4pvp4CI7tmLZ6lS26VTbosLKM/edit#).
|
||||
* [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP0VMOZ-V7-5AchXTHAQFzJw).
|
||||
* Secrets Store CSI Meeting: [Thursdays at 8:00 PT (Pacific Time)](https://zoom.us/j/91272289538) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=8:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* Secrets Store CSI Meeting: [Thursdays at 9:00 PT (Pacific Time)](https://zoom.us/j/91272289538) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1q74nboAg0GSPcom3kLWCIoWg43Qg3mr306KNL58f2hg/edit#).
|
||||
* [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP0PCFJrlpV6_nR_j_3RtnwI).
|
||||
* Weekly Issues/PR Triage Meeting: [Mondays at 9:00 PT (Pacific Time)](https://zoom.us/j/264572674) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:00&tz=PT%20%28Pacific%20Time%29).
|
||||
|
|
@ -38,8 +38,8 @@ The Technical Leads of the SIG establish new subprojects, decommission existing
|
|||
subprojects, and resolve cross-subproject technical issues and decisions.
|
||||
|
||||
* David Eads (**[@deads2k](https://github.com/deads2k)**), Red Hat
|
||||
* Mo Khan (**[@enj](https://github.com/enj)**), Microsoft
|
||||
* Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**), Google
|
||||
* Mike Danese (**[@mikedanese](https://github.com/mikedanese)**), Google
|
||||
|
||||
## Emeritus Leads
|
||||
|
||||
|
|
@ -59,7 +59,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
|
|||
- [@kubernetes/sig-auth-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-auth-pr-reviews) - PR Reviews
|
||||
- [@kubernetes/sig-auth-proposals](https://github.com/orgs/kubernetes/teams/sig-auth-proposals) - Design Proposals
|
||||
- [@kubernetes/sig-auth-test-failures](https://github.com/orgs/kubernetes/teams/sig-auth-test-failures) - Test Failures and Triage
|
||||
- Steering Committee Liaison: Christoph Blecker (**[@cblecker](https://github.com/cblecker)**)
|
||||
- Steering Committee Liaison: Patrick Ohly (**[@pohly](https://github.com/pohly)**)
|
||||
|
||||
## Working Groups
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ The [charter](charter.md) defines the scope and governance of the Autoscaling Sp
|
|||
|
||||
## Meetings
|
||||
*Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-autoscaling) for the group will typically add invites for the following meetings to your calendar.*
|
||||
* Regular SIG Meeting: [Mondays at 16:00 Poland](https://zoom.us/j/944410904) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=16:00&tz=Poland).
|
||||
* Regular SIG Meeting: [Mondays at 16:00 Poland](https://zoom.us/j/96548204174) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=16:00&tz=Poland).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1RvhQAEIrVLHbyNnuaT99-6u9ZUMp7BfkPupT2LAZK7w/edit).
|
||||
|
||||
## Leadership
|
||||
|
|
@ -37,7 +37,7 @@ The Chairs of the SIG run operations and processes governing the SIG.
|
|||
- [@kubernetes/sig-autoscaling-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-autoscaling-pr-reviews) - PR Reviews
|
||||
- [@kubernetes/sig-autoscaling-proposals](https://github.com/orgs/kubernetes/teams/sig-autoscaling-proposals) - Design Proposals
|
||||
- [@kubernetes/sig-autoscaling-test-failures](https://github.com/orgs/kubernetes/teams/sig-autoscaling-test-failures) - Test Failures and Triage
|
||||
- Steering Committee Liaison: Tim Pepper (**[@tpepper](https://github.com/tpepper)**)
|
||||
- Steering Committee Liaison: Maciej Szulik (**[@soltysh](https://github.com/soltysh)**)
|
||||
|
||||
## Working Groups
|
||||
|
||||
|
|
@ -53,17 +53,17 @@ The following [subprojects][subproject-definition] are owned by sig-autoscaling:
|
|||
- [kubernetes/autoscaler/addon-resizer](https://github.com/kubernetes/autoscaler/blob/master/addon-resizer/OWNERS)
|
||||
### cluster-autoscaler
|
||||
- **Owners:**
|
||||
- [kubernetes/autoscaler](https://github.com/kubernetes/autoscaler/blob/master/OWNERS)
|
||||
- [kubernetes/autoscaler/cluster-autoscaler](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/OWNERS)
|
||||
### horizontal-pod-autoscaler
|
||||
- **Owners:**
|
||||
- [kubernetes/api/autoscaling](https://github.com/kubernetes/api/blob/master/autoscaling/OWNERS)
|
||||
- [kubernetes/kubernetes/pkg/controller/podautoscaler](https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/podautoscaler/OWNERS)
|
||||
### scale-client
|
||||
### karpenter
|
||||
- **Owners:**
|
||||
- [kubernetes/client-go/scale](https://github.com/kubernetes/client-go/blob/master/scale/OWNERS)
|
||||
- [kubernetes-sigs/karpenter](https://github.com/kubernetes-sigs/karpenter/blob/main/OWNERS)
|
||||
### vertical-pod-autoscaler
|
||||
- **Owners:**
|
||||
- [kubernetes/autoscaler](https://github.com/kubernetes/autoscaler/blob/master/OWNERS)
|
||||
- [kubernetes/autoscaler/vertical-pod-autoscaler](https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/OWNERS)
|
||||
|
||||
[subproject-definition]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects
|
||||
[working-group-definition]: https://github.com/kubernetes/community/blob/master/governance.md#working-groups
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
|
|||
- [@kubernetes/sig-cli-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-cli-pr-reviews) - PR Reviews
|
||||
- [@kubernetes/sig-cli-proposals](https://github.com/orgs/kubernetes/teams/sig-cli-proposals) - Design Proposals
|
||||
- [@kubernetes/sig-cli-test-failures](https://github.com/orgs/kubernetes/teams/sig-cli-test-failures) - Test Failures and Triage
|
||||
- Steering Committee Liaison: Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**)
|
||||
- Steering Committee Liaison: Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**)
|
||||
|
||||
## Subprojects
|
||||
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
|
|||
- [@kubernetes/sig-cloud-provider-proposals](https://github.com/orgs/kubernetes/teams/sig-cloud-provider-proposals) - Design Proposals
|
||||
- [@kubernetes/sig-cloud-provider-test-failures](https://github.com/orgs/kubernetes/teams/sig-cloud-provider-test-failures) - Test Failures and Triage
|
||||
- [@kubernetes/sig-cloud-providers-misc](https://github.com/orgs/kubernetes/teams/sig-cloud-providers-misc) - General Discussion
|
||||
- Steering Committee Liaison: Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**)
|
||||
- Steering Committee Liaison: Maciej Szulik (**[@soltysh](https://github.com/soltysh)**)
|
||||
|
||||
## Working Groups
|
||||
|
||||
|
|
@ -66,6 +66,7 @@ The following [subprojects][subproject-definition] are owned by sig-cloud-provid
|
|||
### cloud-provider-extraction-migration
|
||||
- **Owners:**
|
||||
- [kubernetes-sigs/apiserver-network-proxy](https://github.com/kubernetes-sigs/apiserver-network-proxy/blob/master/OWNERS)
|
||||
- [kubernetes-sigs/cloud-pv-admission-labeler](https://github.com/kubernetes-sigs/cloud-pv-admission-labeler/blob/main/OWNERS)
|
||||
- [kubernetes/community/sig-cloud-provider/cloud-provider-extraction-migration](https://github.com/kubernetes/community/blob/master/sig-cloud-provider/cloud-provider-extraction-migration/OWNERS)
|
||||
- [kubernetes/legacy-cloud-providers](https://github.com/kubernetes/legacy-cloud-providers/blob/master/OWNERS)
|
||||
- **Meetings:**
|
||||
|
|
@ -99,7 +100,7 @@ The following [subprojects][subproject-definition] are owned by sig-cloud-provid
|
|||
- [kubernetes-sigs/provider-aws-test-infra](https://github.com/kubernetes-sigs/provider-aws-test-infra/blob/master/OWNERS)
|
||||
- [kubernetes/cloud-provider-aws](https://github.com/kubernetes/cloud-provider-aws/blob/master/OWNERS)
|
||||
- **Meetings:**
|
||||
- Regular AWS Subproject Meeting: [Fridays at 9:00 PT (Pacific Time)](https://zoom.us/my/k8ssigaws) (biweekly 2019 start date: Jan. 11th). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:00&tz=PT%20%28Pacific%20Time%29).
|
||||
- Regular AWS Subproject Meeting: [Fridays at 9:00 PT (Pacific Time)](https://zoom.us/j/508079177?pwd=ZmEvMksxdTFTc0N1eXFLRm91QUlyUT09) (biweekly 2019 start date: Jan. 11th). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:00&tz=PT%20%28Pacific%20Time%29).
|
||||
- [Meeting notes and Agenda](https://docs.google.com/document/d/1-i0xQidlXnFEP9fXHWkBxqySkXwJnrGJP9OGyP2_P14/edit).
|
||||
- [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP29DzPOBBaJi-SO3AQ_b4HC).
|
||||
### provider-azure
|
||||
|
|
|
|||
|
|
@ -4,16 +4,12 @@
|
|||
|
||||
1. What work did the SIG do this year that should be highlighted?
|
||||
|
||||
-
|
||||
-
|
||||
-
|
||||
- In 2022, SIG Cloud Provider made progress in the extraction migration process with the [Openstack in-tree provider removal](https://github.com/kubernetes/kubernetes/pull/67782).
|
||||
- We merged the [KEP for CCM webhooks](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2699-add-webhook-hosting-to-ccm), finalizing the design. This was to solve a problem around persistent volume labeling and to allow for further customization.
|
||||
|
||||
2. What initiatives are you working on that aren't being tracked in KEPs?
|
||||
|
||||
-
|
||||
-
|
||||
-
|
||||
|
||||
- Michael McCune (@elmiko) began [experimental work on e2e test refactors](https://hackmd.io/@elmiko/BJGn1SQU3), building a set of generic ccm tests, based on the current tests, that will be available for all providers to utilize to exercise their own provider. We currently have limited tests for selected providers, and want to expand beyond that.
|
||||
|
||||
|
||||
3. KEP work in 2022 (v1.24, v1.25, v1.26):
|
||||
|
|
@ -22,6 +18,7 @@
|
|||
- stable:
|
||||
- [1959 - Service Type=LoadBalancer Class Field](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/1959-service-lb-class-field) - v1.24
|
||||
- [2436 - Controller Manager Leader Migration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2436-controller-manager-leader-migration) - v1.24
|
||||
- [2133: Kubelet Credential Providers](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2133-kubelet-credential-providers) - v1.26
|
||||
|
||||
|
||||
## Project health
|
||||
|
|
@ -29,46 +26,46 @@
|
|||
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)
|
||||
|
||||
-
|
||||
-
|
||||
-
|
||||
- While we always need stronger connections to the individual cloud providers and better representation across the community, we specifically could use help with the individual cloud provider implementations. Most providers have a relatively small subset of active maintainers compared to other SIGs in Kubernetes overall. (The OWNERS files appear to need an audit.)
|
||||
|
||||
2. What metrics/community health stats does your group care about and/or measure?
|
||||
|
||||
-
|
||||
-
|
||||
-
|
||||
- SIG Cloud Provider monitors the number and variety of cloud providers who are attending SIG meetings and providing feedback about their concerns with issues on their infrastructures or with difficulties implementing SIG-owned keps and related technical assistance. We measure this through attendance and agenda items at our bi-weekly SIG meetings.
|
||||
|
||||
|
||||
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?
|
||||
|
||||
-
|
||||
- Given the vendor-specific nature of the out-of-tree cloud provider code bases, when new potential contributors ask about opportunities we recommend they look at the provider for the cloud they are most interested in using. Pairing with an established contributor or partnering on a bugfix is a good approach. We welcome documentation contributions for topics like how CCMs work (and also docs about release engineering, QA, and testing).
|
||||
|
||||
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]?
|
||||
|
||||
-
|
||||
- Our SIG has no special requirements beyond the general contributor guide.
|
||||
|
||||
|
||||
5. Does the group have contributors from multiple companies/affiliations?
|
||||
|
||||
-
|
||||
- Yes, SIG Cloud Provider has contributors from multiple clouds and large-scale vendors. The nature of cross-cloud and cross-vendor collaboration means that it’s necessary to have contributors from the major areas of cloud effort in the ecosystem.
|
||||
|
||||
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?
|
||||
|
||||
-
|
||||
-
|
||||
- Interested users who work at end user organizations can contribute to the cloud provider work via testing, bug reports, and feature requests. They can also contribute to the specific individual provider codebases as relevant to their needs.
|
||||
|
||||
## 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 -->
|
||||
Note: Estimated numbers as of July 2023 when data was collected; 2022 numbers not available.
|
||||
|
||||
Include any other ways you measure group membership
|
||||
|
||||
- Primary slack channel member count: 1,157
|
||||
- Primary mailing list member count: 265
|
||||
- Primary meeting attendee count (estimated, if needed): ~6-8 (estimate/average)
|
||||
- Primary meeting participant count (estimated, if needed): ~5-6 (estimate/average)
|
||||
- Unique reviewers for SIG-owned packages: 109
|
||||
- Unique approvers for SIG-owned packages: 116
|
||||
|
||||
Note: for 2022, we retrieved reviewer and approver numbers from all the subprojects listed in https://github.com/kubernetes/community/tree/master/sig-cloud-provider#subprojects which means this figure is not comparable to the limited subset counted in 2021. However, a cursory overview of the OWNERS files reveals that they change infrequently and likely need an audit.
|
||||
|
||||
## [Subprojects](https://git.k8s.io/community/sig-cloud-provider#subprojects)
|
||||
|
||||
|
|
@ -104,15 +101,16 @@ Include any other ways you measure group membership
|
|||
|
||||
Operational tasks in [sig-governance.md]:
|
||||
|
||||
- [ ] [README.md] reviewed for accuracy and updated if needed
|
||||
- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
|
||||
- [X] [README.md] reviewed for accuracy and updated if needed
|
||||
- [X] [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:
|
||||
-
|
||||
- [X] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
|
||||
- [X] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
|
||||
- [X] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed
|
||||
- [X] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
|
||||
- KubeCon EU 2022 - [SIG Cloud Provider: Portable K8s Across all Clouds, Roadmap and Updates - Nick Turner, Amazon & Steve Wong, VMware](https://sched.co/ytow)
|
||||
- KubeCon NA 2022 - [SIG Cloud Provider Update - Michael McCune, Red Hat & Bridget Kromhout, Microsoft](https://www.youtube.com/watch?v=jnc4Eysh1g0) & [slides](https://sched.co/1C89O)
|
||||
-
|
||||
|
||||
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cloud-provider/CONTRIBUTING.md
|
||||
|
|
|
|||
|
|
@ -71,6 +71,7 @@ A project for figuring out the best way to install, manage and deliver cluster a
|
|||
A project focused on providing declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters
|
||||
- **Owners:**
|
||||
- [kubernetes-sigs/cluster-api](https://github.com/kubernetes-sigs/cluster-api/blob/main/OWNERS)
|
||||
- [kubernetes-sigs/logical-cluster](https://github.com/kubernetes-sigs/logical-cluster/blob/main/OWNERS)
|
||||
- **Contact:**
|
||||
- Slack: [#cluster-api](https://kubernetes.slack.com/messages/cluster-api)
|
||||
- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle)
|
||||
|
|
@ -82,6 +83,9 @@ A project focused on providing declarative APIs and tooling to simplify provisio
|
|||
Implementation of Cluster Add-on Provider for Helm, an add-on orchestration solution for Cluster API using Helm.
|
||||
- **Owners:**
|
||||
- [kubernetes-sigs/cluster-api-addon-provider-helm](https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/blob/main/OWNERS)
|
||||
- **Contact:**
|
||||
- Slack: [#cluster-api-addon-helm](https://kubernetes.slack.com/messages/cluster-api-addon-helm)
|
||||
- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle)
|
||||
### cluster-api-ipam-provider-in-cluster
|
||||
Cluster API IPAM provider
|
||||
- **Owners:**
|
||||
|
|
@ -261,10 +265,6 @@ A project that uses Ansible / Vagrant for deploying production ready clusters on
|
|||
- **Contact:**
|
||||
- Slack: [#kubespray](https://kubernetes.slack.com/messages/kubespray)
|
||||
- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle)
|
||||
### logical-cluster
|
||||
A set of APIs to improve the Kubernetes user experience for cluster administration by offering utilities to interact with fleet of clusters which can be managed by Cluster API, or other entities (like cloud providers).
|
||||
- **Owners:**
|
||||
- [kubernetes-sigs/logical-cluster](https://github.com/kubernetes-sigs/logical-cluster/blob/main/OWNERS)
|
||||
### minikube
|
||||
Implements a local Kubernetes cluster for application development on macOS, Linux, and Windows
|
||||
- **Owners:**
|
||||
|
|
|
|||
|
|
@ -23,9 +23,7 @@ The [charter](charter.md) defines the scope and governance of the Contributor Ex
|
|||
### Chairs
|
||||
The Chairs of the SIG run operations and processes governing the SIG.
|
||||
|
||||
* Josh Berkus (**[@jberkus](https://github.com/jberkus)**), Red Hat
|
||||
* Kaslin Fields (**[@kaslin](https://github.com/kaslin)**), Google
|
||||
* Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**), Google
|
||||
* Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**), VMware
|
||||
|
||||
### Technical Leads
|
||||
|
|
@ -34,15 +32,17 @@ subprojects, and resolve cross-subproject technical issues and decisions.
|
|||
|
||||
* Madhav Jivrajani (**[@MadhavJivrajani](https://github.com/MadhavJivrajani)**), VMware
|
||||
* Priyanka Saggu (**[@Priyankasaggu11929](https://github.com/Priyankasaggu11929)**), SUSE
|
||||
* Christoph Blecker (**[@cblecker](https://github.com/cblecker)**), Red Hat
|
||||
* Nikhita Raghunath (**[@nikhita](https://github.com/nikhita)**), VMware
|
||||
|
||||
## Emeritus Leads
|
||||
|
||||
* Elsie Phillips (**[@Phillels](https://github.com/Phillels)**)
|
||||
* Alison Dowdney (**[@alisondy](https://github.com/alisondy)**)
|
||||
* Jorge Castro (**[@castrojo](https://github.com/castrojo)**)
|
||||
* Christoph Blecker (**[@cblecker](https://github.com/cblecker)**)
|
||||
* Garrett Rodrigues (**[@grodrigues3](https://github.com/grodrigues3)**)
|
||||
* Josh Berkus (**[@jberkus](https://github.com/jberkus)**)
|
||||
* Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**)
|
||||
* Nikhita Raghunath (**[@nikhita](https://github.com/nikhita)**)
|
||||
* Paris Pittman (**[@parispittman](https://github.com/parispittman)**)
|
||||
|
||||
## Contact
|
||||
|
|
@ -70,7 +70,6 @@ Manages operations and policy for upstream community group communication platfor
|
|||
### contributor-comms
|
||||
Contributor Communications focuses on amplifying the success of Kubernetes contributors through marketing.
|
||||
- **Owners:**
|
||||
- [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets/blob/master/OWNERS)
|
||||
- [kubernetes-sigs/lwkd](https://github.com/kubernetes-sigs/lwkd/blob/main/OWNERS)
|
||||
- [kubernetes/community/communication/contributor-comms](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/OWNERS)
|
||||
- **Meetings:**
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ The [charter](charter.md) defines the scope and governance of the Docs Special I
|
|||
* New Contributor Meet and Greet: [Tuesdays at 10:30 UTC](https://zoom.us/j/92822621820?pwd=S1p4RnB1RmNSZ3JjYlRRUVd4UjFPZz09) (first Tuesday of the month). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=10:30&tz=UTC).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1emuO4nmaQq3K8JZ9-MQeIygtrCPO9kWv7U7RzTaW4F8/).
|
||||
* [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP3b5hlx0YV7Lo7DtckM84y8).
|
||||
* Regular SIG Meeting: [Tuesdays at 17:30 UTC](https://docs.google.com/document/d/1emuO4nmaQq3K8JZ9-MQeIygtrCPO9kWv7U7RzTaW4F8/edit) (weekly - except fourth Tuesday every month). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=17:30&tz=UTC).
|
||||
* Regular SIG Meeting: [Tuesdays at 17:30 UTC](https://docs.google.com/document/d/1emuO4nmaQq3K8JZ9-MQeIygtrCPO9kWv7U7RzTaW4F8/edit) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=17:30&tz=UTC).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1emuO4nmaQq3K8JZ9-MQeIygtrCPO9kWv7U7RzTaW4F8/edit).
|
||||
* [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP3b5hlx0YV7Lo7DtckM84y8).
|
||||
* Spanish Team Meeting: [Tuesdays at 15:30 UTC](https://zoom.us/j/95918289494?pwd=Wk9Oa0xZUkFXSDV5OTFoZEZsTURCZz09) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=15:30&tz=UTC).
|
||||
|
|
@ -39,7 +39,7 @@ The [charter](charter.md) defines the scope and governance of the Docs Special I
|
|||
The Chairs of the SIG run operations and processes governing the SIG.
|
||||
|
||||
* Divya Mohan (**[@divya-mohan0209](https://github.com/divya-mohan0209)**), SUSE
|
||||
* Natali Vlatko (**[@natalisucks](https://github.com/natalisucks)**), Wayfair
|
||||
* Natali Vlatko (**[@natalisucks](https://github.com/natalisucks)**), Cisco
|
||||
* Rey Lejano (**[@reylejano](https://github.com/reylejano)**), SUSE
|
||||
|
||||
### Technical Leads
|
||||
|
|
@ -47,7 +47,7 @@ The Technical Leads of the SIG establish new subprojects, decommission existing
|
|||
subprojects, and resolve cross-subproject technical issues and decisions.
|
||||
|
||||
* Karen Bradshaw (**[@kbhawkey](https://github.com/kbhawkey)**), Independent
|
||||
* Taylor Dolezal (**[@onlydole](https://github.com/onlydole)**), Independent
|
||||
* Taylor Dolezal (**[@onlydole](https://github.com/onlydole)**), CNCF
|
||||
* Tim Bannister (**[@sftim](https://github.com/sftim)**), The Scale Factory
|
||||
* Qiming Teng (**[@tengqm](https://github.com/tengqm)**), Sangfor Technologies
|
||||
|
||||
|
|
@ -83,7 +83,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
|
|||
- [@kubernetes/sig-docs-ru-owners](https://github.com/orgs/kubernetes/teams/sig-docs-ru-owners) - Russian language content
|
||||
- [@kubernetes/sig-docs-uk-owners](https://github.com/orgs/kubernetes/teams/sig-docs-uk-owners) - Ukrainian language content
|
||||
- [@kubernetes/sig-docs-zh-owners](https://github.com/orgs/kubernetes/teams/sig-docs-zh-owners) - Chinese language content
|
||||
- Steering Committee Liaison: Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**)
|
||||
- Steering Committee Liaison: Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**)
|
||||
|
||||
## Subprojects
|
||||
|
||||
|
|
|
|||
|
|
@ -1,43 +1,46 @@
|
|||
# Kubernetes Blog Subproject
|
||||
|
||||
The Kubernetes Blog Subproject is owned by [SIG-Docs](https://github.com/kubernetes/community/tree/master/sig-docs) and run by the [Editorial Team](#leadership).
|
||||
The Kubernetes Blog Subproject is owned by [SIG Docs](https://github.com/kubernetes/community/tree/master/sig-docs).
|
||||
|
||||
This section covers documentation, processes, and roles for the [Kubernetes blog](https://kubernetes.io/blog/).
|
||||
|
||||
## Meetings
|
||||
|
||||
Regular Blog Meeting: Tuesdays at 18:30 UTC (biweekly). [Convert Your Timezone](http://www.thetimezoneconverter.com/?t=18:30&tz=UTC)
|
||||
See [meetings](/kubernetes/community/tree/master/sig-docs#meetings) for SIG Docs
|
||||
|
||||
- [Meeting notes and Agenda](https://docs.google.com/document/d/1W5MKkaQGd3YKKZINzj1tJAQbql5R_Y4KAHlFNsJ44Bc/edit?usp=sharing)
|
||||
- [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP3b5hlx0YV7Lo7DtckM84y8)
|
||||
|
||||
## Leadership
|
||||
## Subproject contributors
|
||||
|
||||
- **Technical Editors:** [Bob Killen](https://github.com/mrbobbytables), [Taylor Dolezal](https://github.com/onlydole), [Tim Bannister](https://github.com/sftim), [Nate Waddington](https://github.com/nate-double-u)
|
||||
<!-- GitHub username alphabetical order -->
|
||||
- **Blog approvers:** [Bob Killen](https://github.com/mrbobbytables), [Taylor Dolezal](https://github.com/onlydole),
|
||||
[Nate Waddington](https://github.com/nate-double-u), [Tim Bannister](https://github.com/sftim)
|
||||
|
||||
- **Blog shadow approvers:** _no contributors_
|
||||
|
||||
- **Blog editors:** _no contributors_
|
||||
|
||||
- **Blog shadow editors:** _no contributors_
|
||||
|
||||
✨ Could **you** join the blog editorial team?
|
||||
|
||||
## Contact
|
||||
|
||||
- Slack: [#sig-docs-blog](https://kubernetes.slack.com/messages/CJDHVD54J)
|
||||
- Mailing List: [blog@kubernetes.io](mailto:blog@kubernetes.io)
|
||||
- Open Community Issues/PRs: [`is:open repo:kubernetes/website label:area/blog`](https://github.com/issues?q=is%3Aopen+label%3Aarea%2Fblog+repo%3Akubernetes%2Fwebsite)
|
||||
- GitHub Teams: [@kubernetes/kubernetes-blog](https://github.com/orgs/kubernetes/teams/kubernetes-blog), [@kubernetes/kubernetes-blog-maintainers](https://github.com/orgs/kubernetes/teams/kubernetes-blog-maintainers)
|
||||
|
||||
## Submit a Post
|
||||
|
||||
Anyone can write a blog post and submit it for review. Blog posts should not be commercial in nature and should consist of content that will apply broadly to the Kubernetes community.
|
||||
|
||||
To submit a blog post, follow the steps below.
|
||||
To propose a blog post, read [Submitting blog posts and case studies](https://k8s.io/docs/contribute/new-content/blogs-case-studies/).
|
||||
|
||||
1. [Sign the CLA](https://kubernetes.io/docs/contribute/start/#sign-the-cla) if you have not yet done so.
|
||||
1. Have a look at the Markdown format for existing blog posts in the [website repository](https://github.com/kubernetes/website/tree/master/content/en/blog/_posts).
|
||||
1. Write out your blog post in a text editor of your choice.
|
||||
1. On the same link from step 2, click the Create new file button. Paste your content into the editor. Name the file to match the proposed title of the blog post, but don’t put the date in the file name. The blog reviewers will work with you on the final file name and the date the blog will be published.
|
||||
1. When you save the file, GitHub will walk you through the pull request process.
|
||||
1. A blog post reviewer will review your submission and work with you on feedback and final details. When the blog post is approved, the blog will be scheduled for publication.
|
||||
### Article guidelines
|
||||
|
||||
### Blog Guidelines
|
||||
**Original content only**. You cannot submit a blog article that has been published elsewhere. The Kubernetes project
|
||||
makes exception to this only for articles posted to the CNCF blog or to the [Kubernetes contributor blog](https://k8s.dev/blog/).
|
||||
|
||||
Requested Content (with examples):
|
||||
Requested content:
|
||||
|
||||
- New Kubernetes capabilities
|
||||
- Kubernetes projects updates
|
||||
|
|
@ -45,50 +48,61 @@ Requested Content (with examples):
|
|||
- Tutorials and walkthroughs
|
||||
- Thought leadership around Kubernetes
|
||||
- Kubernetes Partner OSS integration
|
||||
- **Original content only**
|
||||
|
||||
Unsuitable Content:
|
||||
Unsuitable content:
|
||||
|
||||
- Vendor product pitches
|
||||
- Partner updates without an integration and customer story
|
||||
- Syndicated posts (language translations ok)
|
||||
- Syndicated posts (it's OK to localized existing articles from English)
|
||||
|
||||
## Review Process
|
||||
## Review process
|
||||
|
||||
Once a blog post is submitted either via the form or a PR, it will be routed to the editorial team for review either via email for Google Docs or auto-assigning for a PR.
|
||||
|
||||
Each blog post requires a LGTM from one copy editor, technical editor\*, and blog community manager. Once the necessary LGTMs are in place, an Editorial Lead will schedule and approve the blog post.
|
||||
Each blog post requires a LGTM from a blog editor (or approver) and an approval by a blog approver. Blog editors will usually also get a technical review from the appropriate SIG.
|
||||
|
||||
_If a blog post does not contain any technical content (for example, [How You Can Help Localize Kubernetes Docs](https://kubernetes.io/blog/2019/04/26/how-you-can-help-localize-kubernetes-docs/)), the technical review can be omitted._
|
||||
|
||||
### Embargoed Content
|
||||
Articles should merge _before_ their publication date; automation picks up scheduled posts and publishes them automatically.
|
||||
|
||||
The blog repository on GitHub is public, therefore any content that needs to remain confidential until a certain time (for example: release posts, security vulnerabilities) should be proposed by email message to [blog@kubernetes.io](mailto:blog@kubernetes.io). In your message, please note the time that the embargo will be lifted.
|
||||
|
||||
### Release communications
|
||||
|
||||
SIG Release lead on blog articles to announce Kubernetes releases, and the post-release series of articles. SIG Docs and the blog subproject support
|
||||
that process and provide approvals for upcoming articles.
|
||||
|
||||
### Embargoed content
|
||||
|
||||
The blog repository on GitHub is public, therefore any content that needs to remain confidential until a certain time (for example: release posts, security vulnerabilities) should be proposed by email message to [blog@kubernetes.io](mailto:blog@kubernetes.io). If you need to, you can also send a Slack direct message to the set of blog approvers; please do this sparingly.
|
||||
|
||||
In your message, please note the time that the embargo will be lifted.
|
||||
|
||||
### SLA
|
||||
|
||||
Blog posts can take up to **2 weeks** to review. If you’d like to request an expedited review, please email [blog@kubernetes.io](mailto:blog@kubernetes.io).
|
||||
Blog posts can take up to **4 weeks** to review. If you’d like to request an expedited review, please get in touch via [#sig-docs-blog](https://app.slack.com/client/T09NY5SBT/CJDHVD54J) on the Kubernetes Slack workspace.
|
||||
|
||||
## Ongoing Blog Maintenance
|
||||
## Ongoing blog maintenance
|
||||
|
||||
SIG-Docs approvers for English content can approve edits after the fact such as: broken links, copy edits, etc. However, approval and editorial review for new blog posts is limited to the Blog Team.
|
||||
SIG Docs approvers for English content can approve edits after the fact such as: broken links, copy edits, etc. However, approval and editorial review for new blog posts is limited to the Blog Team.
|
||||
|
||||
We typically do not make edits to blog posts more than 1 years old.
|
||||
We typically do not make edits to blog posts more than 1 years old; there is an exception for articles marked `evergreen: true` in their
|
||||
[front matter](https://gohugo.io/content-management/front-matter/).
|
||||
|
||||
## Editorial Team Selection
|
||||
## Editorial team selection
|
||||
|
||||
Each Editorial Team role is responsible for staffing their respective role, with this order of fall-through in mind:
|
||||
Bloggers and reviewer responsibilities include staffing the team, with this order of fall-through in mind:
|
||||
|
||||
- training and selecting a successor from the current pool of role shadows
|
||||
- training and selecting a successor from non-Editorial Team members
|
||||
- staffing the role themselves
|
||||
|
||||
Ultimately, if none of these can be satisfied, responsibility falls to the Editorial Team Lead and SIG-Docs to staff the roles.
|
||||
Ultimately, if none of these can be satisfied, responsibility falls to the SIG Docs leadership to staff the roles.
|
||||
|
||||
### Shadows
|
||||
|
||||
We are always open to adding new shadows to the editorial team roles. If you are interested in shadowing one of the roles on the team, please fill out [this application](The application form is now live for anyone interested in joining the blog editorial team: https://docs.google.com/forms/d/e/1FAIpQLScg9fHsyW-LlsBF8rc9J0sR8u3O3g17lwFUKIE-qrjL6Z-AyA/viewform?usp=sf_link). We review applications on a rolling basis.
|
||||
We are always open to adding new shadows to the editorial team roles. If you are interested in shadowing one of the roles on the team, please say Hi in
|
||||
[#sig-docs-blog](https://app.slack.com/client/T09NY5SBT/CJDHVD54J) on the Kubernetes Slack workspace. Visit https://slack.k8s.io/ for an invitation if you are not already part of the workspace.
|
||||
|
||||
### Removing a Team Member
|
||||
### Removing a team member
|
||||
|
||||
If a team member can no longer fulfill their duties, the role defaults to the shadow.
|
||||
If all members of a group (eg approvers) can no longer fulfil their duties, and there is a shadow for that role, that role defaults to the shadow.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,8 @@
|
|||
# See the OWNERS docs at https://go.k8s.io/owners
|
||||
|
||||
reviewers:
|
||||
- sig-etcd-leads
|
||||
approvers:
|
||||
- sig-etcd-leads
|
||||
labels:
|
||||
- sig/etcd
|
||||
|
|
@ -0,0 +1,118 @@
|
|||
<!---
|
||||
This is an autogenerated file!
|
||||
|
||||
Please do not edit this file directly, but instead make changes to the
|
||||
sigs.yaml file in the project root.
|
||||
|
||||
To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
|
||||
--->
|
||||
# etcd Special Interest Group
|
||||
|
||||
etcd is a production-ready store for building cloud-native distributed systems and managing cloud-native infrastructure via orchestrators like Kubernetes.
|
||||
Etcd should provide distributed system primitives** (such as distributed locking and leader election) that allow users to **create scalable, highly available and fault-tolerant systems.
|
||||
Etcd is the place to store the infrastructure configuration, not only as part of Kubernetes, but also as a standalone solution.
|
||||
|
||||
The [charter](charter.md) defines the scope and governance of the etcd Special Interest Group.
|
||||
|
||||
## Meetings
|
||||
*Joining the [mailing list](https://groups.google.com/g/etcd-dev) for the group will typically add invites for the following meetings to your calendar.*
|
||||
* Regular SIG Meeting: [Thursdays at 11:00 PT (Pacific Time)](https://zoom.us/my/cncfetcdproject) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=11:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/16XEGyPBisZvmmoIHSZzv__LoyOeluC5a4x353CX0SIM/edit?usp=sharing).
|
||||
* [Meeting recordings](https://www.youtube.com/playlist?list=PLRGL688DpO9rtufHbiunuCHddYY6MGkwW).
|
||||
|
||||
## Leadership
|
||||
|
||||
### Chairs
|
||||
The Chairs of the SIG run operations and processes governing the SIG.
|
||||
|
||||
* James Blair (**[@jmhbnz](https://github.com/jmhbnz)**), Red Hat
|
||||
* Wenjia Zhang (**[@wenjiaswe](https://github.com/wenjiaswe)**), Google
|
||||
|
||||
### Technical Leads
|
||||
The Technical Leads of the SIG establish new subprojects, decommission existing
|
||||
subprojects, and resolve cross-subproject technical issues and decisions.
|
||||
|
||||
* Benjamin Wang (**[@ahrtr](https://github.com/ahrtr)**), VMWare
|
||||
* Marek Siarkowicz (**[@serathius](https://github.com/serathius)**), Google
|
||||
|
||||
## Contact
|
||||
- Slack: [#etcd](https://kubernetes.slack.com/messages/etcd)
|
||||
- [Mailing list](https://groups.google.com/g/etcd-dev)
|
||||
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fetcd)
|
||||
- GitHub Teams:
|
||||
- [@kubernetes/sig-etcd-leads](https://github.com/orgs/kubernetes/teams/sig-etcd-leads) - SIG Chairs and Tech Leads
|
||||
- Steering Committee Liaison: Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**)
|
||||
|
||||
## Subprojects
|
||||
|
||||
The following [subprojects][subproject-definition] are owned by sig-etcd:
|
||||
### bbolt
|
||||
An embedded key/value database for Go.
|
||||
- **Owners:**
|
||||
- [etcd-io/bbolt/MAINTAINERS](https://github.com/etcd-io/bbolt/blob/master/MAINTAINERS)
|
||||
### cetcd
|
||||
Serve Consul with etcd
|
||||
- **Owners:**
|
||||
- [etcd-io/cetcd/MAINTAINERS](https://github.com/etcd-io/cetcd/blob/master/MAINTAINERS)
|
||||
### dbtester
|
||||
Distributed database benchmark tester
|
||||
- **Owners:**
|
||||
- [etcd-io/dbtester/MAINTAINERS](https://github.com/etcd-io/dbtester/blob/master/MAINTAINERS)
|
||||
### discovery.etcd.io
|
||||
Kubernetes manifests powering discovery.etcd.io
|
||||
- **Owners:**
|
||||
- [etcd-io/discovery.etcd.io/MAINTAINERS](https://github.com/etcd-io/discovery.etcd.io/blob/master/MAINTAINERS)
|
||||
### discoveryserver
|
||||
Public etcd Discovery Service
|
||||
- **Owners:**
|
||||
- [etcd-io/discoveryserver/MAINTAINERS](https://github.com/etcd-io/discoveryserver/blob/master/MAINTAINERS)
|
||||
### etcd
|
||||
Distributed reliable key-value store for the most critical data of a distributed system
|
||||
- **Owners:**
|
||||
- [etcd-io/etcd/MAINTAINERS](https://github.com/etcd-io/etcd/blob/master/MAINTAINERS)
|
||||
### etcd-play
|
||||
etcd playground
|
||||
- **Owners:**
|
||||
- [etcd-io/etcd-play/MAINTAINERS](https://github.com/etcd-io/etcd-play/blob/master/MAINTAINERS)
|
||||
### etcdlabs
|
||||
etcd playground
|
||||
- **Owners:**
|
||||
- [etcd-io/etcdlabs/MAINTAINERS](https://github.com/etcd-io/etcdlabs/blob/master/MAINTAINERS)
|
||||
### gofail
|
||||
failpoints for go
|
||||
- **Owners:**
|
||||
- [etcd-io/gofail/MAINTAINERS](https://github.com/etcd-io/gofail/blob/master/MAINTAINERS)
|
||||
### govanityurls
|
||||
Use a custom domain in your Go import path
|
||||
- **Owners:**
|
||||
- [etcd-io/govanityurls/MAINTAINERS](https://github.com/etcd-io/govanityurls/blob/master/MAINTAINERS)
|
||||
### jetcd
|
||||
etcd java client
|
||||
- **Owners:**
|
||||
- [etcd-io/jetcd/MAINTAINERS](https://github.com/etcd-io/jetcd/blob/master/MAINTAINERS)
|
||||
### maintainers
|
||||
issue tracking for project wide non-code concerns
|
||||
- **Owners:**
|
||||
- [etcd-io/maintainers/MAINTAINERS](https://github.com/etcd-io/maintainers/blob/master/MAINTAINERS)
|
||||
### protodoc
|
||||
protodoc generates Protocol Buffer documentation.
|
||||
- **Owners:**
|
||||
- [etcd-io/protodoc/MAINTAINERS](https://github.com/etcd-io/protodoc/blob/master/MAINTAINERS)
|
||||
### raft
|
||||
Raft library for maintaining a replicated state machine
|
||||
- **Owners:**
|
||||
- [etcd-io/raft/MAINTAINERS](https://github.com/etcd-io/raft/blob/master/MAINTAINERS)
|
||||
### website
|
||||
etcd-io
|
||||
- **Owners:**
|
||||
- [etcd-io/website/MAINTAINERS](https://github.com/etcd-io/website/blob/master/MAINTAINERS)
|
||||
### zetcd
|
||||
Serve the Apache Zookeeper API but back it with an etcd cluster
|
||||
- **Owners:**
|
||||
- [etcd-io/zetcd/MAINTAINERS](https://github.com/etcd-io/zetcd/blob/master/MAINTAINERS)
|
||||
|
||||
[subproject-definition]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects
|
||||
[working-group-definition]: https://github.com/kubernetes/community/blob/master/governance.md#working-groups
|
||||
<!-- BEGIN CUSTOM CONTENT -->
|
||||
|
||||
<!-- END CUSTOM CONTENT -->
|
||||
|
|
@ -0,0 +1,63 @@
|
|||
# SIG etcd Charter
|
||||
|
||||
This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
|
||||
the Roles and Organization Management outlined in [sig-governance].
|
||||
|
||||
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
|
||||
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
|
||||
|
||||
## Scope
|
||||
|
||||
Owns the etcd project and how it is used by Kubernetes.
|
||||
|
||||
### In scope
|
||||
|
||||
#### Code, Binaries and Services
|
||||
|
||||
- Development of [etcd] and other repositories under [etcd-io organization]
|
||||
- Maintenance of [etcd image] packaged with Kubernetes
|
||||
|
||||
[etcd]: https://github.com/etcd-io/etcd
|
||||
[etcd-io organization]: https://github.com/etcd-io
|
||||
[etcd image]: https://github.com/kubernetes/kubernetes/tree/master/cluster/images/etcd
|
||||
|
||||
#### Cross-cutting and Externally Facing Processes
|
||||
|
||||
- Specifying, testing and improving the implicit Kubernetes-ETCD Contract, which includes storage requirements, write and delete requirements, read requirements and watch requirements.
|
||||
- Release process of etcd and other binaries belonging to [etcd-io organization]
|
||||
|
||||
### Out of scope
|
||||
|
||||
- Structure of data stored in etcd by Kubernetes components is owned by SIG API Machinery
|
||||
|
||||
## Roles and Organization Management
|
||||
|
||||
This SIG follows the Roles and Organization Management outlined in [sig-governance]
|
||||
and opts-in to updates and modifications to [sig-governance].
|
||||
|
||||
### Additional responsibilities of Tech Leads
|
||||
|
||||
- Release of etcd and other binaries belonging to [etcd-io organization]
|
||||
|
||||
### Deviations from [sig-governance]
|
||||
|
||||
- SIG etcd's participation in the Kubernetes release cycle is limited by etcd having a different schedule for its releases.
|
||||
- SIG etcd communication utilizes pre-existing forums for communication:
|
||||
- Email: [etcd-dev](https://groups.google.com/forum/?hl=en#!forum/etcd-dev).
|
||||
- Slack: [#etcd](https://kubernetes.slack.com/messages/C3HD8ARJ5/details/) channel on Kubernetes.
|
||||
- SIG etcd contributing instructions ([CONTRIBUTING.md]) be defined in etcd project.
|
||||
|
||||
[CONTRIBUTING.md]: https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md
|
||||
|
||||
### Deviations from [kubernetes-repositories]
|
||||
|
||||
- SIG etcd repositories live in github.com/etcd-io
|
||||
- SIG etcd repositories should (but not must) adopt merge bot, Kubernetes PR commands/bot.
|
||||
- SIG etcd repositories will follow [rules for donated repositories].
|
||||
|
||||
[kubernetes-repositories]: https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#sig-repositories
|
||||
[rules for donated repositories]: https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#rules-for-donated-repositories
|
||||
|
||||
### Subproject Creation
|
||||
|
||||
By SIG Technical Leads
|
||||
|
|
@ -0,0 +1,100 @@
|
|||
# SIG etcd Vision
|
||||
|
||||
The long-term success of the etcd project depends on the following:
|
||||
- Etcd is a reliable key-value storage
|
||||
- Etcd is simple to operate
|
||||
- Etcd is a standalone solution for managing infrastructure
|
||||
- Etcd scales beyond Kubernetes dimensions
|
||||
|
||||
The goals and milestones listed here are for future releases.
|
||||
The scope of release v3.6 has already been defined and is unlikely to change.
|
||||
|
||||
## Etcd is a reliable key-value storage service
|
||||
|
||||
Reliability remains the most important property of etcd.
|
||||
The project cannot allow for another [data inconsistency incident].
|
||||
If we could only pick one thing from the list of goals above, this would be it.
|
||||
No matter what features we add in the future,
|
||||
they must not diminish etcd's reliability.
|
||||
We must establish processes and safeguards to prevent future incidents.
|
||||
|
||||
How?
|
||||
- Etcd API guarantees are well understood, documented and tested.
|
||||
- Etcd adopts a production readiness review process for new features, similar to Kubernetes one.
|
||||
- Robustness tests should cover most of the API and most common failures.
|
||||
- New features must have accompanying e2e tests and be covered by robustness tests.
|
||||
- Etcd must be able to immediately detect corruption.
|
||||
- Etcd must be able to automatically recover from data corruption.
|
||||
|
||||
[data inconsistency incident]: https://github.com/etcd-io/etcd/blob/main/Documentation/postmortems/v3.5-data-inconsistency.md
|
||||
|
||||
## Etcd is simple to operate
|
||||
|
||||
Etcd should be easy to operate.
|
||||
Currently, there are many steps involved in operating etcd,
|
||||
and some of these steps require external tools.
|
||||
For example, Kubernetes provides tools to [downgrade/upgrade etcd].
|
||||
These tools are not part of the etcd,
|
||||
but they are available as part of the Kubernetes distribution of etcd.
|
||||
|
||||
How?
|
||||
- Etcd should not require users to run periodic defrag
|
||||
- Etcd officially supports live upgrades and downgrades
|
||||
- Disaster recovery for Etcd & Kubernetes
|
||||
- Reliable cluster membership changes via learners with automated promotion
|
||||
- Two node etcd clusters
|
||||
|
||||
## Etcd is a standalone solution for managing infrastructure configuration
|
||||
|
||||
Kubernetes is not the only way to manage infrastructure.
|
||||
It was the first to introduce many concepts that have now become the standard,
|
||||
but they are not unique to Kubernetes.
|
||||
The most important design principle of Kubernetes,
|
||||
the reconciliation protocol, is not something unique to it.
|
||||
|
||||
Reconciliation can be implemented solely on etcd,
|
||||
as has been shown by projects like Cillium,
|
||||
Calico Typha that support etcd-based control planes.
|
||||
The reason why this idea has not propagated further is
|
||||
the amount of work that was put into making
|
||||
the reconciliation protocol scale in Kubernetes.
|
||||
The watch cache is a key part of this scaling,
|
||||
and it is not part of the etcd project.
|
||||
|
||||
If etcd provided a Kubernetes-like storage interface
|
||||
and primitives for the reconciliation protocol,
|
||||
it would be a more viable solution for managing infrastructure.
|
||||
This would allow users to build etcd-based control planes that
|
||||
could scale to meet the needs of large and complex deployments.
|
||||
|
||||
How?
|
||||
- Introduce Kubernetes like storage interface into etcd-client
|
||||
- Provide etcd primitives for reconciliation protocol
|
||||
- Strip out the Kubernetes watch cache and make it part of the etcd client.
|
||||
- Use the watch cache in the client to build an eventually consistent etcd proxy.
|
||||
|
||||
[downgrade/upgrade etcd]: https://github.com/kubernetes/kubernetes/tree/master/cluster/images/etcd
|
||||
|
||||
## Etcd scales beyond Kubernetes dimensions
|
||||
|
||||
Etcd has proven its scalability by enabling Kubernetes clusters of up to 5,000 nodes.
|
||||
However, as the cloud native ecosystem has evolved, new projects have been built on top of Kubernetes.
|
||||
These projects, such as [KCP] (a multi-cluster control plane) and [Kueue] (a batch job queuing system),
|
||||
have different scalability requirements than pure Kubernetes.
|
||||
For example, they need support for larger storage sizes and higher throughput.
|
||||
|
||||
Etcd's strong points are its reliable raft and efficient watch implementation.
|
||||
However, its storage capabilities are not as strong.
|
||||
To address this, we should look into growing out storage capabilities and making them more flexible depending on the use case.
|
||||
|
||||
How?
|
||||
- Well-defined and tested scalability dimensions
|
||||
- Increase raft throughput (async and batch proposal handling)
|
||||
- Increasing bbolt supported storage size
|
||||
- Pluggable storage layer
|
||||
- Hybrid clusters with write and read optimized members
|
||||
|
||||
|
||||
[KCP]: https://cloud.redhat.com/blog/an-introduction-to-kcp
|
||||
[Kueue]: https://github.com/kubernetes-sigs/kueue
|
||||
|
||||
|
|
@ -47,7 +47,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
|
|||
- [@kubernetes/sig-instrumentation-approvers](https://github.com/orgs/kubernetes/teams/sig-instrumentation-approvers) - SIG Top-level Approvers
|
||||
- [@kubernetes/sig-instrumentation-leads](https://github.com/orgs/kubernetes/teams/sig-instrumentation-leads) - SIG Chairs and Tech Leads
|
||||
- [@kubernetes/sig-instrumentation-members](https://github.com/orgs/kubernetes/teams/sig-instrumentation-members) - SIG Membership Roster
|
||||
- Steering Committee Liaison: Christoph Blecker (**[@cblecker](https://github.com/cblecker)**)
|
||||
- Steering Committee Liaison: Patrick Ohly (**[@pohly](https://github.com/pohly)**)
|
||||
|
||||
## Working Groups
|
||||
|
||||
|
|
|
|||
|
|
@ -25,18 +25,21 @@ The [charter](charter.md) defines the scope and governance of the K8s Infra Spec
|
|||
The Chairs of the SIG run operations and processes governing the SIG.
|
||||
|
||||
* Arnaud Meukam (**[@ameukam](https://github.com/ameukam)**), VMware
|
||||
* Davanum Srinivas (**[@dims](https://github.com/dims)**), Amazon Web Services
|
||||
* Davanum Srinivas (**[@dims](https://github.com/dims)**), Amazon
|
||||
|
||||
### Technical Leads
|
||||
The Technical Leads of the SIG establish new subprojects, decommission existing
|
||||
subprojects, and resolve cross-subproject technical issues and decisions.
|
||||
|
||||
* Aaron Crickenberger (**[@spiffxp](https://github.com/spiffxp)**), Google
|
||||
* Tim Hockin (**[@thockin](https://github.com/thockin)**), Google
|
||||
* Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**), Google
|
||||
* Arnaud Meukam (**[@ameukam](https://github.com/ameukam)**), VMware
|
||||
* Mahamed Ali (**[@upodroid](https://github.com/upodroid)**), Cisco
|
||||
|
||||
## Emeritus Leads
|
||||
|
||||
* Bart Smykla (**[@bartsmykla](https://github.com/bartsmykla)**)
|
||||
* Aaron Crickenberger (**[@spiffxp](https://github.com/spiffxp)**)
|
||||
* Tim Hockin (**[@thockin](https://github.com/thockin)**)
|
||||
|
||||
## Contact
|
||||
- Slack: [#sig-k8s-infra](https://kubernetes.slack.com/messages/sig-k8s-infra)
|
||||
|
|
|
|||
31
sig-list.md
31
sig-list.md
|
|
@ -32,49 +32,50 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
|
|||
|
||||
| Name | Label | Chairs | Contact | Meetings |
|
||||
|------|-------|--------|---------|----------|
|
||||
|[API Machinery](sig-api-machinery/README.md)|[api-machinery](https://github.com/kubernetes/kubernetes/labels/sig%2Fapi-machinery)|* [David Eads](https://github.com/deads2k), Red Hat<br>* [Federico Bongiovanni](https://github.com/fedebongio), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-api-machinery)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-api-machinery)|* Kubebuilder and Controller Runtime Meeting: [Thursdays at 11:00 PT (Pacific Time) (biweekly)]()<br>* Regular SIG Meeting: [Wednesdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/my/apimachinery)<br>
|
||||
|[API Machinery](sig-api-machinery/README.md)|[api-machinery](https://github.com/kubernetes/kubernetes/labels/sig%2Fapi-machinery)|* [David Eads](https://github.com/deads2k), Red Hat<br>* [Federico Bongiovanni](https://github.com/fedebongio), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-api-machinery)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-api-machinery)|* Kubebuilder Meeting: [Thursdays at 11:00 PT (Pacific Time) (biweekly)]()<br>* Regular SIG Meeting: [Wednesdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/my/apimachinery)<br>
|
||||
|[Apps](sig-apps/README.md)|[apps](https://github.com/kubernetes/kubernetes/labels/sig%2Fapps)|* [Janet Kuo](https://github.com/janetkuo), Google<br>* [Kenneth Owens](https://github.com/kow3ns), Snowflake<br>* [Maciej Szulik](https://github.com/soltysh), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-apps)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-apps)|* Regular SIG Meeting: [Mondays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/739385290?pwd=ekVmNGRjT214MGJkY1JUUUpPMVlJUT09)<br>
|
||||
|[Architecture](sig-architecture/README.md)|[architecture](https://github.com/kubernetes/kubernetes/labels/sig%2Farchitecture)|* [Derek Carr](https://github.com/derekwaynecarr), Red Hat<br>* [Davanum Srinivas](https://github.com/dims), Amazon Web Services<br>* [John Belamaric](https://github.com/johnbelamaric), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-architecture)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-architecture)|* Enhancements Subproject Meeting: [Thursdays at 10:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/95357819945)<br>* Production Readiness Office Hours: [Wednesdays at 12:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/482444151)<br>* Regular SIG Meeting: [Thursdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/845605479)<br>* code organization Office Hours: [Thursdays at 14:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/159990793)<br>* conformance office Hours: [Wednesdays at 18:00 UTC (First Wednesday of the month)](https://zoom.us/j/427337923)<br>
|
||||
|[Auth](sig-auth/README.md)|[auth](https://github.com/kubernetes/kubernetes/labels/sig%2Fauth)|* [Mo Khan](https://github.com/enj), Microsoft<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>* Weekly Issues/PR Triage Meeting: [Mondays at 9:00 PT (Pacific Time) (weekly)](https://zoom.us/j/264572674)<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>
|
||||
|[Architecture](sig-architecture/README.md)|[architecture](https://github.com/kubernetes/kubernetes/labels/sig%2Farchitecture)|* [Derek Carr](https://github.com/derekwaynecarr), Red Hat<br>* [Davanum Srinivas](https://github.com/dims), Amazon<br>* [John Belamaric](https://github.com/johnbelamaric), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-architecture)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-architecture)|* Enhancements Subproject Meeting: [Thursdays at 10:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/95357819945)<br>* Production Readiness Office Hours: [Wednesdays at 12:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/482444151)<br>* Regular SIG Meeting: [Thursdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/845605479)<br>* code organization Office Hours: [Thursdays at 14:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/159990793)<br>* conformance office Hours: [Wednesdays at 18:00 UTC (First Wednesday of the month)](https://zoom.us/j/427337923)<br>
|
||||
|[Auth](sig-auth/README.md)|[auth](https://github.com/kubernetes/kubernetes/labels/sig%2Fauth)|* [Mo Khan](https://github.com/enj), Microsoft<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 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/91272289538)<br>* Weekly Issues/PR Triage Meeting: [Mondays at 9:00 PT (Pacific Time) (weekly)](https://zoom.us/j/264572674)<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/96548204174)<br>
|
||||
|[CLI](sig-cli/README.md)|[cli](https://github.com/kubernetes/kubernetes/labels/sig%2Fcli)|* [Katrina Verey](https://github.com/KnVerey), Independent<br>* [Eddie Zaneski](https://github.com/eddiezane), Chainguard, Inc<br>* [Natasha Sarkar](https://github.com/natasha41575), 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) (every four weeks)](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) (every four weeks)](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)|* [Bridget Kromhout](https://github.com/bridgetkromhout), Microsoft<br>* [Michael McCune](https://github.com/elmiko), Red Hat<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: [Tuesdays at 16:00 PT (Pacific Time) (monthly - third Tuesday)](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-oci) Regular Oracle Cloud Subproject Meeting: [Tuesdays at 06:00 PT (Pacific Time) (First Tuesday of each month)](https://oracle.zoom.us/j/99910180651?pwd=MjhhVC9jZjU3eGIxdjNTYm1UU3V6dz09)<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)|* [Bridget Kromhout](https://github.com/bridgetkromhout), Microsoft<br>* [Michael McCune](https://github.com/elmiko), Red Hat<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/j/508079177?pwd=ZmEvMksxdTFTc0N1eXFLRm91QUlyUT09)<br>* (provider-azure) Azure Subproject Meeting: [Tuesdays at 16:00 PT (Pacific Time) (monthly - third Tuesday)](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-oci) Regular Oracle Cloud Subproject Meeting: [Tuesdays at 06:00 PT (Pacific Time) (First Tuesday of each month)](https://oracle.zoom.us/j/99910180651?pwd=MjhhVC9jZjU3eGIxdjNTYm1UU3V6dz09)<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), Red Hat<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 09:00 PT (Pacific Time) (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-openstack) Cluster API Provider OpenStack Office Hours: [Wednesdays at 14:00 UTC (alternate weeks, check agenda doc for last meeting)](https://zoom.us/j/91405526408?pwd=bVBxempwVDBzejJGQlhSOGlXZnRxUT09)<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: [Mondays at 08:30 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)|* [Josh Berkus](https://github.com/jberkus), Red Hat<br>* [Kaslin Fields](https://github.com/kaslin), Google<br>* [Bob Killen](https://github.com/mrbobbytables), Google<br>* [Nabarun Pal](https://github.com/palnabarun), VMware<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 - Contributor Comms Team Meeting: [Fridays at 8:00 PT (Pacific Time) (weekly)](https://zoom.us/j/596959769?pwd=TURBNlZPb3BEWVFmbWlCYXlMVVJiUT09)<br>* (github-management) GitHub Administration Subproject: [Thursdays at 09:00 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>* [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 Subproject Meeting: [Mondays at 15:00 UTC (first Monday of the month)](https://docs.google.com/document/d/1NwO1AN8Ea2zlK8uAdaDAKf1-LZDAFvSewIfrKqfl5No/)<br>* New Contributor Meet and Greet: [Tuesdays at 10:30 UTC (first Tuesday of the month)](https://zoom.us/j/92822621820?pwd=S1p4RnB1RmNSZ3JjYlRRUVd4UjFPZz09)<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>
|
||||
|[Contributor Experience](sig-contributor-experience/README.md)|[contributor-experience](https://github.com/kubernetes/kubernetes/labels/sig%2Fcontributor-experience)|* [Kaslin Fields](https://github.com/kaslin), Google<br>* [Nabarun Pal](https://github.com/palnabarun), VMware<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 - Contributor Comms Team Meeting: [Fridays at 8:00 PT (Pacific Time) (weekly)](https://zoom.us/j/596959769?pwd=TURBNlZPb3BEWVFmbWlCYXlMVVJiUT09)<br>* (github-management) GitHub Administration Subproject: [Thursdays at 09:00 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>* [Natali Vlatko](https://github.com/natalisucks), Cisco<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 Subproject Meeting: [Mondays at 15:00 UTC (first Monday of the month)](https://docs.google.com/document/d/1NwO1AN8Ea2zlK8uAdaDAKf1-LZDAFvSewIfrKqfl5No/)<br>* New Contributor Meet and Greet: [Tuesdays at 10:30 UTC (first Tuesday of the month)](https://zoom.us/j/92822621820?pwd=S1p4RnB1RmNSZ3JjYlRRUVd4UjFPZz09)<br>* Regular SIG Meeting: [Tuesdays at 17:30 UTC (biweekly)](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>
|
||||
|[etcd](sig-etcd/README.md)|[etcd](https://github.com/kubernetes/kubernetes/labels/sig%2Fetcd)|* [James Blair](https://github.com/jmhbnz), Red Hat<br>* [Wenjia Zhang](https://github.com/wenjiaswe), Google<br>|* [Slack](https://kubernetes.slack.com/messages/etcd)<br>* [Mailing List](https://groups.google.com/g/etcd-dev)|* Regular SIG Meeting: [Thursdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/my/cncfetcdproject)<br>
|
||||
|[Instrumentation](sig-instrumentation/README.md)|[instrumentation](https://github.com/kubernetes/kubernetes/labels/sig%2Finstrumentation)|* [Elana Hashman](https://github.com/ehashman), Apple<br>* [Han Kang](https://github.com/logicalhan), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-instrumentation)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-instrumentation)|* Regular SIG Meeting: [Thursdays at 9:30 PT (Pacific Time) (biweekly)](https://zoom.us/j/5342565819?pwd=RlVsK21NVnR1dmE3SWZQSXhveHZPdz09)<br>* Regular Triage Meeting: [Thursdays at 9:30 PT (Pacific Time) (biweekly - alternating with regular meeting)](https://zoom.us/j/5342565819?pwd=RlVsK21NVnR1dmE3SWZQSXhveHZPdz09)<br>
|
||||
|[K8s Infra](sig-k8s-infra/README.md)|[k8s-infra](https://github.com/kubernetes/kubernetes/labels/sig%2Fk8s-infra)|* [Arnaud Meukam](https://github.com/ameukam), VMware<br>* [Davanum Srinivas](https://github.com/dims), Amazon Web Services<br>|* [Slack](https://kubernetes.slack.com/messages/sig-k8s-infra)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-k8s-infra)|* Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s-infra-dns) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s-infra-groups) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s.io) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (porche) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (registry.k8s.io) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>
|
||||
|[K8s Infra](sig-k8s-infra/README.md)|[k8s-infra](https://github.com/kubernetes/kubernetes/labels/sig%2Fk8s-infra)|* [Arnaud Meukam](https://github.com/ameukam), VMware<br>* [Davanum Srinivas](https://github.com/dims), Amazon<br>|* [Slack](https://kubernetes.slack.com/messages/sig-k8s-infra)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-k8s-infra)|* Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s-infra-dns) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s-infra-groups) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s.io) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (porche) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (registry.k8s.io) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>
|
||||
|[Multicluster](sig-multicluster/README.md)|[multicluster](https://github.com/kubernetes/kubernetes/labels/sig%2Fmulticluster)|* [Jeremy Olmsted-Thompson](https://github.com/jeremyot), Google<br>* [Paul Morie](https://github.com/pmorie), Apple<br>|* [Slack](https://kubernetes.slack.com/messages/sig-multicluster)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-multicluster)|* Regular SIG Meeting: [Tuesdays at 9:30 PT (Pacific Time) (bi-weekly)](https://zoom.us/my/k8s.mc)<br>
|
||||
|[Network](sig-network/README.md)|[network](https://github.com/kubernetes/kubernetes/labels/sig%2Fnetwork)|* [Michael Zappa](https://github.com/mikezappa87), Microsoft<br>* [Shane Utt](https://github.com/shaneutt), Kong<br>* [Tim Hockin](https://github.com/thockin), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-network)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-network)|* Gateway API Code Jam: [Fridays at 08:30 PT (Pacific Time) (Last Friday of the Month)](https://zoom.us/j/96900767253)<br>* Gateway API GAMMA Meeting (APAC Friendly): [Tuesdays at 15:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API GAMMA Meeting (EMEA Friendly): [Tuesdays at 08:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API Meeting: [Mondays at 15:00 PT (Pacific Time) (weekly)](https://zoom.us/j/441530404)<br>* Network Policy API Meeting: [Tuesdays at 9:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/96264742248)<br>* SIG Network Ingress NGINX Meeting: [Thursdays at 8:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/98377891310)<br>* SIG Network KPNG APAC Meeting: [Wednesdays at 16:00 IST (Indian Standard Time) (weekly)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit)<br>* SIG Network KPNG Meeting: [Fridays at 7:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit)<br>* SIG Network Meeting: [Thursdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/361123509)<br>* SIG Network Multi-Network Meeting: [Wednesdays at 08:00 PT (Pacific Time) (weekly)](https://zoom.us/j/95680858961?pwd=M1c2TTdMZHpMUUtIYXRpbjRobkNJZz09)<br>
|
||||
|[Network](sig-network/README.md)|[network](https://github.com/kubernetes/kubernetes/labels/sig%2Fnetwork)|* [Michael Zappa](https://github.com/mikezappa87), Microsoft<br>* [Shane Utt](https://github.com/shaneutt), Kong<br>* [Tim Hockin](https://github.com/thockin), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-network)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-network)|* Gateway API GAMMA Meeting (APAC Friendly): [Tuesdays at 15:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API GAMMA Meeting (EMEA Friendly): [Tuesdays at 08:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API Meeting: [Mondays at 15:00 PT (Pacific Time) (weekly)](https://zoom.us/j/441530404)<br>* Network Policy API Meeting: [Tuesdays at 9:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/96264742248)<br>* SIG Network Ingress NGINX Meeting: [Thursdays at 8:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/98377891310)<br>* SIG Network Meeting: [Thursdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/361123509)<br>* SIG Network Multi-Network Meeting: [Wednesdays at 08:00 PT (Pacific Time) (weekly)](https://zoom.us/j/95680858961?pwd=M1c2TTdMZHpMUUtIYXRpbjRobkNJZz09)<br>* Sig-Network Code Jam: [Fridays at 08:30 PT (Pacific Time) (Last Friday of the Month)](https://zoom.us/j/96900767253)<br>
|
||||
|[Node](sig-node/README.md)|[node](https://github.com/kubernetes/kubernetes/labels/sig%2Fnode)|* [Sergey Kanzhelev](https://github.com/SergeyKanzhelev), Google<br>* [Mrunal Patel](https://github.com/mrunalp), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-node)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-node)|* Main SIG Meeting: [Tuesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/4799874685)<br>* Weekly CI/Triage Meeting: [Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/4799874685)<br>
|
||||
|[Release](sig-release/README.md)|[release](https://github.com/kubernetes/kubernetes/labels/sig%2Frelease)|* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Stephen Augustus](https://github.com/justaugustus), Cisco<br>* [Sascha Grunert](https://github.com/saschagrunert), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-release)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-release)|* Regular SIG Meeting APAC/EU Oriented Time: [Tuesdays at 14:30 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br>* Regular SIG Meeting US Oriented Time: [Tuesdays at 17:00 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br>
|
||||
|[Scalability](sig-scalability/README.md)|[scalability](https://github.com/kubernetes/kubernetes/labels/sig%2Fscalability)|* [Marcel Zieba](https://github.com/marseel), Google<br>* [Shyam Jeedigunta](https://github.com/shyamjvs), AWS<br>|* [Slack](https://kubernetes.slack.com/messages/sig-scalability)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scale)|* Regular SIG Meeting: [Thursdays at 10:30 PT (Pacific Time) (bi-weekly ([upcoming meeting dates](#upcoming-meeting-dates)))](https://zoom.us/j/94252896018?pwd=cTlMMlBoTHZqUEdjRm9VY2NWNUg5dz09)<br>
|
||||
|[Scalability](sig-scalability/README.md)|[scalability](https://github.com/kubernetes/kubernetes/labels/sig%2Fscalability)|* [Marcel Zieba](https://github.com/marseel), Isovalent<br>* [Shyam Jeedigunta](https://github.com/shyamjvs), Amazon<br>|* [Slack](https://kubernetes.slack.com/messages/sig-scalability)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scale)|* Regular SIG Meeting: [Thursdays at 10:30 PT (Pacific Time) (bi-weekly ([upcoming meeting dates](#upcoming-meeting-dates)))](https://zoom.us/j/94252896018?pwd=cTlMMlBoTHZqUEdjRm9VY2NWNUg5dz09)<br>
|
||||
|[Scheduling](sig-scheduling/README.md)|[scheduling](https://github.com/kubernetes/kubernetes/labels/sig%2Fscheduling)|* [Wei Huang](https://github.com/Huang-Wei), Apple<br>* [Abdullah Gharaibeh](https://github.com/ahg-g), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-scheduling)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scheduling)|* biweekly meeting (NA & Europe): [Thursdays at 17:00 UTC (biweekly starting Thursday June 7, 2018)](https://zoom.us/j/841218129)<br>* descheduler biweekly meeting: [Tuesdays at 17:00 UTC (biweekly starting Tuesday September 13, 2022)](https://zoom.us/j/841218129)<br>* monthly meeting (APAC): [first Thursdays at 02:00 UTC (monthly)](https://zoom.us/j/841218129)<br>
|
||||
|[Security](sig-security/README.md)|[security](https://github.com/kubernetes/kubernetes/labels/sig%2Fsecurity)|* [Ian Coldwater](https://github.com/IanColdwater), Twilio<br>* [Tabitha Sable](https://github.com/tabbysable), Datadog<br>|* [Slack](https://kubernetes.slack.com/messages/sig-security)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-security)|* Regular SIG Meeting: [Thursdays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/9934z1184192?pwd=L25Tc0ZOL3FqU09KNERlTU12dFhTQT09)<br>
|
||||
|[Storage](sig-storage/README.md)|[storage](https://github.com/kubernetes/kubernetes/labels/sig%2Fstorage)|* [Saad Ali](https://github.com/saad-ali), Google<br>* [Xing Yang](https://github.com/xing-yang), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/sig-storage)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-storage)|* Regular CSI Implementation meeting: [Monday and Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/614261834)<br>* Regular SIG Meeting: [Thursdays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/614261834)<br>
|
||||
|[Testing](sig-testing/README.md)|[testing](https://github.com/kubernetes/kubernetes/labels/sig%2Ftesting)|* [Brady Pratt](https://github.com/jbpratt), Red Hat<br>* [Michelle Shepardson](https://github.com/michelle192837), Google<br>* [Brian McQueen](https://github.com/xmcqueen), LinkedIn<br>|* [Slack](https://kubernetes.slack.com/messages/sig-testing)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-testing)|* SIG Testing Bi-Weekly Meeting: [Tuesdays at 10:00 PT (Pacific Time) (bi-weekly starting Tuesday August 13, 2019)](https://zoom.us/j/135450138?pwd=WGJyaVZzekJCWFBTMGJGTXVjUFJaUT09)<br>
|
||||
|[UI](sig-ui/README.md)|[ui](https://github.com/kubernetes/kubernetes/labels/sig%2Fui)|* [Sebastian Florek](https://github.com/floreks), Kubermatic<br>* [Marcin Maciaszczyk](https://github.com/maciaszczykm), Kubermatic<br>* [Shu Muto](https://github.com/shu-mutou), NEC<br>|* [Slack](https://kubernetes.slack.com/messages/sig-ui)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-ui)|* Regular SIG Meeting: [Thursdays at 09:00 PT (Pacific Time) (bi-weekly)](https://groups.google.com/forum/#!forum/kubernetes-sig-ui)<br>
|
||||
|[Windows](sig-windows/README.md)|[windows](https://github.com/kubernetes/kubernetes/labels/sig%2Fwindows)|* [Aravindh Puthiyaparambil](https://github.com/aravindhp), Redhat<br>* [Mark Rossetti](https://github.com/marosset), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/sig-windows)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-windows)|* Backlog Refinement / Bug Triage Meeting: [Thursdays at 12:30 Eastern Time (ET) (biweekly)](https://zoom.us/j/94389601840?pwd=MCs2SEJQWG0zUWpBS3Nod0ZNMmVXQT09)<br>* Regular SIG Meeting: [Tuesdays at 12:30 Eastern Time (ET) (weekly)](https://zoom.us/j/96892680257?pwd=TVNyMzB4VVMwRGZnUkgzT1dnb2szZz09)<br>* Weekly CI Meeting: [Tuesdays at 12:15 Eastern Time (ET) (weekly)](https://zoom.us/j/96892680257?pwd=TVNyMzB4VVMwRGZnUkgzT1dnb2szZz09)<br>
|
||||
|[Windows](sig-windows/README.md)|[windows](https://github.com/kubernetes/kubernetes/labels/sig%2Fwindows)|* [Aravindh Puthiyaparambil](https://github.com/aravindhp), Red Hat<br>* [Mark Rossetti](https://github.com/marosset), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/sig-windows)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-windows)|* Backlog Refinement / Bug Triage Meeting: [Thursdays at 12:30 Eastern Time (ET) (biweekly)](https://zoom.us/j/94389601840?pwd=MCs2SEJQWG0zUWpBS3Nod0ZNMmVXQT09)<br>* Regular SIG Meeting: [Tuesdays at 12:30 Eastern Time (ET) (weekly)](https://zoom.us/j/96892680257?pwd=TVNyMzB4VVMwRGZnUkgzT1dnb2szZz09)<br>* Weekly CI Meeting: [Tuesdays at 12:15 Eastern Time (ET) (weekly)](https://zoom.us/j/96892680257?pwd=TVNyMzB4VVMwRGZnUkgzT1dnb2szZz09)<br>
|
||||
|
||||
### Working Groups
|
||||
|
||||
| Name | Label | Stakeholder SIGs |Organizers | Contact | Meetings |
|
||||
|------|-------|------------------|-----------|---------|----------|
|
||||
|[API Expression](wg-api-expression/README.md)|[api-expression](https://github.com/kubernetes/kubernetes/labels/wg%2Fapi-expression)|* API Machinery<br>* Architecture<br>|* [Antoine Pelisse](https://github.com/apelisse), Google<br>* [Kevin Wiesmueller](https://github.com/kwiesmueller), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-api-expression)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-api-expression)|* Regular WG Meeting: [Tuesdays at 9:30 PT (Pacific Time) (biweekly)](https://zoom.us/j/94238112084)<br>
|
||||
|[Batch](wg-batch/README.md)|[batch](https://github.com/kubernetes/kubernetes/labels/wg%2Fbatch)|* Apps<br>* Autoscaling<br>* Node<br>* Scheduling<br>|* [Wei Huang](https://github.com/Huang-Wei), Apple<br>* [Abdullah Gharaibeh](https://github.com/ahg-g), Google<br>* [Danielle Lancashire](https://github.com/endocrimes), Independent<br>* [Maciej Szulik](https://github.com/soltysh), Red Hat<br>* [Swati Sehgal](https://github.com/swatisehgal), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-batch)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-batch)|* Regular Meeting ([Calendar](https://calendar.google.com/calendar/embed?src=8ulop9k0jfpuo0t7kp8d9ubtj4%40group.calendar.google.com)): [Thursdays (starting March 3rd 2022)s at 7AM PT (Pacific Time) (biweekly)](https://zoom.us/j/98329676612?pwd=c0N2bVV1aTh2VzltckdXSitaZXBKQT09)<br>
|
||||
|[Batch](wg-batch/README.md)|[batch](https://github.com/kubernetes/kubernetes/labels/wg%2Fbatch)|* Apps<br>* Autoscaling<br>* Node<br>* Scheduling<br>|* [Wei Huang](https://github.com/Huang-Wei), Apple<br>* [Danielle Lancashire](https://github.com/endocrimes), Independent<br>* [Marcin Wielgus](https://github.com/mwielgus), Google<br>* [Maciej Szulik](https://github.com/soltysh), Red Hat<br>* [Swati Sehgal](https://github.com/swatisehgal), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-batch)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-batch)|* Regular Meeting ([Calendar](https://calendar.google.com/calendar/embed?src=8ulop9k0jfpuo0t7kp8d9ubtj4%40group.calendar.google.com)): [Thursdays (starting March 3rd 2022)s at 7AM PT (Pacific Time) (biweekly)](https://zoom.us/j/98329676612?pwd=c0N2bVV1aTh2VzltckdXSitaZXBKQT09)<br>
|
||||
|[Data Protection](wg-data-protection/README.md)|[data-protection](https://github.com/kubernetes/kubernetes/labels/wg%2Fdata-protection)|* Apps<br>* Storage<br>|* [Xing Yang](https://github.com/xing-yang), VMware<br>* [Xiangqian Yu](https://github.com/yuxiangqian), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-data-protection)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-data-protection)|* Regular WG Meeting: [Wednesdays at 9:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/6933410772)<br>
|
||||
|[IoT Edge](wg-iot-edge/README.md)|[iot-edge](https://github.com/kubernetes/kubernetes/labels/wg%2Fiot-edge)|* Multicluster<br>* Network<br>|* [Steve Wong](https://github.com/cantbewong), VMware<br>* [Cindy Xing](https://github.com/cindyxing), Microsoft<br>* [Dejan Bosanac](https://github.com/dejanb), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-iot-edge)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-iot-edge)|* APAC WG Meeting: [Wednesdays at 5:00 UTC (every four weeks)](https://zoom.us/j/91251176046?pwd=cmdqclovM3R3eDB1VlpuL1ZGU1hnZz09)<br>* Regular WG Meeting (Pacific Time): [Wednesdays at 09:00 PT (every four weeks)](https://zoom.us/j/92778512626?pwd=MXhlemwvYnhkQmkxeXllQ0Z5VGs4Zz09)<br>
|
||||
|[LTS](wg-lts/README.md)|[lts](https://github.com/kubernetes/kubernetes/labels/wg%2Flts)|* Architecture<br>* Cluster Lifecycle<br>* K8s Infra<br>* Release<br>* Security<br>* Testing<br>|* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Jordan Liggitt](https://github.com/liggitt), Google<br>* [Micah Hausler](https://github.com/micahhausler), Amazon<br>|* [Slack](https://kubernetes.slack.com/messages/wg-lts)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-lts)|* Regular WG Meeting: [Tuesdays at 07:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/92480197536?pwd=dmtSMGJRQmNYYTIyZkFlQ25JRngrdz09)<br>
|
||||
|[Policy](wg-policy/README.md)|[policy](https://github.com/kubernetes/kubernetes/labels/wg%2Fpolicy)|* Architecture<br>* Auth<br>* Multicluster<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Jim Bugwadia](https://github.com/JimBugwadia), Kyverno/Nirmata<br>* [Robert Ficcaglia](https://github.com/rficcaglia), SunStone<br>|* [Slack](https://kubernetes.slack.com/messages/wg-policy)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-policy)|* Regular WG Meeting: [Wednesdays at 8:00 PT (Pacific Time) (semimonthly)](https://zoom.us/j/7375677271)<br>
|
||||
|[Structured Logging](wg-structured-logging/README.md)|[structured-logging](https://github.com/kubernetes/kubernetes/labels/wg%2Fstructured-logging)|* API Machinery<br>* Architecture<br>* Cloud Provider<br>* Instrumentation<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Patrick Ohly](https://github.com/pohly), Intel<br>* [Marek Siarkowicz](https://github.com/serathius), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-structured-logging)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging)|* Regular Meeting: [Thursdays at 15:30 London-UK (biweekly)](https://zoom.us/j/96716142646?pwd=VmgrN29sbmhDREp3R0NtZlpGSlZ4Zz09)<br>
|
||||
|[Structured Logging](wg-structured-logging/README.md)|[structured-logging](https://github.com/kubernetes/kubernetes/labels/wg%2Fstructured-logging)|* API Machinery<br>* Architecture<br>* Cloud Provider<br>* Instrumentation<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Mengjiao Liu](https://github.com/mengjiao-liu), DaoCloud<br>* [Patrick Ohly](https://github.com/pohly), Intel<br>|* [Slack](https://kubernetes.slack.com/messages/wg-structured-logging)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging)|
|
||||
|
||||
### Committees
|
||||
|
||||
| Name | Label | Members | Contact |
|
||||
|------|--------|---------|---------|
|
||||
|[Code of Conduct](committee-code-of-conduct/README.md)|[code-of-conduct](https://github.com/kubernetes/kubernetes/labels/committee%2Fcode-of-conduct)|* [Ana Margarita Medina](https://github.com/AnaMMedina21), Lightstep<br>* [Danielle Lancashire](https://github.com/endocrimes), Independent<br>* [Hilliary Lipsig](https://github.com/hlipsig), RedHat<br>* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Xander Grzywinski](https://github.com/salaxander), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/code-of-conduct)<br>* [Private Mailing List](conduct@kubernetes.io)
|
||||
|[Code of Conduct](committee-code-of-conduct/README.md)|[code-of-conduct](https://github.com/kubernetes/kubernetes/labels/committee%2Fcode-of-conduct)|* [Ana Margarita Medina](https://github.com/AnaMMedina21), Lightstep<br>* [Danielle Lancashire](https://github.com/endocrimes), Independent<br>* [Hilliary Lipsig](https://github.com/hlipsig), Red Hat<br>* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Xander Grzywinski](https://github.com/salaxander), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/code-of-conduct)<br>* [Private Mailing List](conduct@kubernetes.io)
|
||||
|[Security Response](committee-security-response/README.md)|[security-response](https://github.com/kubernetes/kubernetes/labels/committee%2Fsecurity-response)|* [Sri Saran Balaji](https://github.com/SaranBalaji90), Amazon<br>* [CJ Cullen](https://github.com/cjcullen), Google<br>* [Craig Ingram](https://github.com/cji), Google<br>* [Mo Khan](https://github.com/enj), Microsoft<br>* [Joel Smith](https://github.com/joelsmith), Red Hat<br>* [Micah Hausler](https://github.com/micahhausler), Amazon<br>* [Rita Zhang](https://github.com/ritazh), Microsoft<br>* [Tabitha Sable](https://github.com/tabbysable), Datadog<br>|* [Private Mailing List](security@kubernetes.io)
|
||||
|[Steering](committee-steering/README.md)|[steering](https://github.com/kubernetes/kubernetes/labels/committee%2Fsteering)|* [Benjamin Elder](https://github.com/BenTheElder), Google<br>* [Christoph Blecker](https://github.com/cblecker), Red Hat<br>* [Carlos Tadeu Panato Jr.](https://github.com/cpanato), Chainguard, Inc<br>* [Stephen Augustus](https://github.com/justaugustus), Cisco<br>* [Bob Killen](https://github.com/mrbobbytables), Google<br>* [Nabarun Pal](https://github.com/palnabarun), VMware<br>* [Tim Pepper](https://github.com/tpepper), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/steering-committee)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/forum/#!forum/steering)<br>* [Private Mailing List](steering-private@kubernetes.io)
|
||||
|[Steering](committee-steering/README.md)|[steering](https://github.com/kubernetes/kubernetes/labels/committee%2Fsteering)|* [Benjamin Elder](https://github.com/BenTheElder), Google<br>* [Stephen Augustus](https://github.com/justaugustus), Cisco<br>* [Bob Killen](https://github.com/mrbobbytables), Google<br>* [Paco Xu 徐俊杰](https://github.com/pacoxu), DaoCloud<br>* [Nabarun Pal](https://github.com/palnabarun), VMware<br>* [Patrick Ohly](https://github.com/pohly), Intel<br>* [Maciej Szulik](https://github.com/soltysh), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/steering-committee)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/forum/#!forum/steering)<br>* [Private Mailing List](steering-private@kubernetes.io)
|
||||
<!-- BEGIN CUSTOM CONTENT -->
|
||||
|
||||
<!-- END CUSTOM CONTENT -->
|
||||
|
|
|
|||
|
|
@ -57,6 +57,9 @@ The following [subprojects][subproject-definition] are owned by sig-multicluster
|
|||
### about-api
|
||||
- **Owners:**
|
||||
- [kubernetes-sigs/about-api](https://github.com/kubernetes-sigs/about-api/blob/master/OWNERS)
|
||||
### cluster-inventory-api
|
||||
- **Owners:**
|
||||
- [kubernetes-sigs/cluster-inventory-api](https://github.com/kubernetes-sigs/cluster-inventory-api/blob/main/OWNERS)
|
||||
### mcs-api
|
||||
- **Owners:**
|
||||
- [kubernetes-sigs/mcs-api](https://github.com/kubernetes-sigs/mcs-api/blob/master/OWNERS)
|
||||
|
|
|
|||
|
|
@ -14,7 +14,6 @@ The [charter](charter.md) defines the scope and governance of the Network Specia
|
|||
|
||||
## Meetings
|
||||
*Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-network) for the group will typically add invites for the following meetings to your calendar.*
|
||||
* Gateway API Code Jam: [Fridays at 08:30 PT (Pacific Time)](https://zoom.us/j/96900767253) (Last Friday of the Month). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=08:30&tz=PT%20%28Pacific%20Time%29).
|
||||
* Gateway API GAMMA Meeting (APAC Friendly): [Tuesdays at 15:00 PT (Pacific Time)](https://zoom.us/j/96951309977) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=15:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1s5hQU0CB9ehjFukRmRHQ41f1FA8GX5_1Rv6nHW6NWAA/edit).
|
||||
* Gateway API GAMMA Meeting (EMEA Friendly): [Tuesdays at 08:00 PT (Pacific Time)](https://zoom.us/j/96951309977) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=08:00&tz=PT%20%28Pacific%20Time%29).
|
||||
|
|
@ -26,14 +25,13 @@ The [charter](charter.md) defines the scope and governance of the Network Specia
|
|||
* SIG Network Ingress NGINX Meeting: [Thursdays at 8:00 PT (Pacific Time)](https://zoom.us/j/98377891310) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=8:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1DKlpcV6DAW0DsBrzh-OLkZvJQmABCVfRIRWBWjc4zOs/edit).
|
||||
* [Meeting recordings](https://www.youtube.com/watch?v=VkbEihIb7tA&list=PL69nYSiGNLP2Rqe8T4mDnyHqDZ4VYPY1X).
|
||||
* SIG Network KPNG APAC Meeting: [Wednesdays at 16:00 IST (Indian Standard Time)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=16:00&tz=IST%20%28Indian%20Standard%20Time%29).
|
||||
* SIG Network KPNG Meeting: [Fridays at 7:30 PT (Pacific Time)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=7:30&tz=PT%20%28Pacific%20Time%29).
|
||||
* SIG Network Meeting: [Thursdays at 09:00 PT (Pacific Time)](https://zoom.us/j/361123509) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=09:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1_w77-zG_Xj0zYvEMfQZTQ-wPP4kXkpGD8smVtW_qqWM/edit).
|
||||
* [Meeting recordings](https://www.youtube.com/watch?v=phCA5-vWkVM&list=PL69nYSiGNLP2E8vmnqo5MwPOY25sDWIxb).
|
||||
* SIG Network Multi-Network Meeting: [Wednesdays at 08:00 PT (Pacific Time)](https://zoom.us/j/95680858961?pwd=M1c2TTdMZHpMUUtIYXRpbjRobkNJZz09) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=08:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1pe_0aOsI35BEsQJ-FhFH9Z_pWQcU2uqwAnOx2NIx6OY/edit).
|
||||
* [Meeting recordings](https://www.youtube.com/watch?v=phCA5-vWkVM&list=PL69nYSiGNLP2E8vmnqo5MwPOY25sDWIxb).
|
||||
* Sig-Network Code Jam: [Fridays at 08:30 PT (Pacific Time)](https://zoom.us/j/96900767253) (Last Friday of the Month). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=08:30&tz=PT%20%28Pacific%20Time%29).
|
||||
|
||||
## Leadership
|
||||
|
||||
|
|
@ -44,6 +42,13 @@ The Chairs of the SIG run operations and processes governing the SIG.
|
|||
* Shane Utt (**[@shaneutt](https://github.com/shaneutt)**), Kong
|
||||
* Tim Hockin (**[@thockin](https://github.com/thockin)**), Google
|
||||
|
||||
### Technical Leads
|
||||
The Technical Leads of the SIG establish new subprojects, decommission existing
|
||||
subprojects, and resolve cross-subproject technical issues and decisions.
|
||||
|
||||
* Dan Winship (**[@danwinship](https://github.com/danwinship)**), Red Hat
|
||||
* Tim Hockin (**[@thockin](https://github.com/thockin)**), Google
|
||||
|
||||
## Emeritus Leads
|
||||
|
||||
* Casey Davenport (**[@caseydavenport](https://github.com/caseydavenport)**)
|
||||
|
|
@ -61,7 +66,7 @@ The Chairs of the SIG run operations and processes governing the SIG.
|
|||
- [@kubernetes/sig-network-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-network-pr-reviews) - PR Reviews
|
||||
- [@kubernetes/sig-network-proposals](https://github.com/orgs/kubernetes/teams/sig-network-proposals) - Design Proposals
|
||||
- [@kubernetes/sig-network-test-failures](https://github.com/orgs/kubernetes/teams/sig-network-test-failures) - Test Failures and Triage
|
||||
- Steering Committee Liaison: Tim Pepper (**[@tpepper](https://github.com/tpepper)**)
|
||||
- Steering Committee Liaison: Maciej Szulik (**[@soltysh](https://github.com/soltysh)**)
|
||||
|
||||
## Working Groups
|
||||
|
||||
|
|
@ -87,6 +92,7 @@ The following [subprojects][subproject-definition] are owned by sig-network:
|
|||
- Slack: [#external-dns](https://kubernetes.slack.com/messages/external-dns)
|
||||
### gateway-api
|
||||
- **Owners:**
|
||||
- [kubernetes-sigs/blixt](https://github.com/kubernetes-sigs/blixt/blob/main/OWNERS)
|
||||
- [kubernetes-sigs/gateway-api](https://github.com/kubernetes-sigs/gateway-api/blob/master/OWNERS)
|
||||
- [kubernetes-sigs/ingress2gateway](https://github.com/kubernetes-sigs/ingress2gateway/blob/main/OWNERS)
|
||||
- [kubernetes/kubernetes/pkg/controller/endpoint](https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/endpoint/OWNERS)
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
|
|||
- [@kubernetes/sig-node-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-node-pr-reviews) - PR Reviews
|
||||
- [@kubernetes/sig-node-proposals](https://github.com/orgs/kubernetes/teams/sig-node-proposals) - Design Proposals
|
||||
- [@kubernetes/sig-node-test-failures](https://github.com/orgs/kubernetes/teams/sig-node-test-failures) - Test Failures and Triage
|
||||
- Steering Committee Liaison: Tim Pepper (**[@tpepper](https://github.com/tpepper)**)
|
||||
- Steering Committee Liaison: Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**)
|
||||
|
||||
## Working Groups
|
||||
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ SIG Technical Leads
|
|||
|
||||
[validation]: /contributors/devel/sig-node/cri-validation.md
|
||||
[testing policy]: /contributors/devel/sig-node/cri-testing-policy.md
|
||||
[test grid]: https://k8s-testgrid.appspot.com/sig-node#Summary
|
||||
[test grid]: https://testgrid.k8s.io/sig-node#Summary
|
||||
[perf dashboard]: http://node-perf-dash.k8s.io/#/builds
|
||||
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
|
||||
[readme]: https://github.com/kubernetes/community/tree/master/sig-node
|
||||
|
|
|
|||
|
|
@ -23,8 +23,8 @@ The [charter](charter.md) defines the scope and governance of the Scalability Sp
|
|||
### Chairs
|
||||
The Chairs of the SIG run operations and processes governing the SIG.
|
||||
|
||||
* Marcel Zieba (**[@marseel](https://github.com/marseel)**), Google
|
||||
* Shyam Jeedigunta (**[@shyamjvs](https://github.com/shyamjvs)**), AWS
|
||||
* Marcel Zieba (**[@marseel](https://github.com/marseel)**), Isovalent
|
||||
* Shyam Jeedigunta (**[@shyamjvs](https://github.com/shyamjvs)**), Amazon
|
||||
|
||||
### Technical Leads
|
||||
The Technical Leads of the SIG establish new subprojects, decommission existing
|
||||
|
|
@ -158,7 +158,8 @@ performance exists (ideally by providing easy-to-use frameworks and working
|
|||
with SIGs to provide them), having environment and resources to run them:
|
||||
|
||||
* [Official tests](https://github.com/kubernetes/perf-tests/tree/master/clusterloader2/testing)
|
||||
* [Testgrid](https://k8s-testgrid.appspot.com/sig-scalability)
|
||||
* [Testgrid](https://testgrid.k8s.io/sig-scalability)
|
||||
* [Perfdash](https://perf-dash.k8s.io/)
|
||||
|
||||
Ensuring that tests are being executed according to calendar and ensuring that
|
||||
each official Kubernetes release satisfies all scalability and performance
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@ None
|
|||
SIG Technical Leads
|
||||
|
||||
|
||||
[test grid]: https://k8s-testgrid.appspot.com/sig-scheduling#Summary
|
||||
[test grid]: https://testgrid.k8s.io/sig-scheduling#Summary
|
||||
[perf dashboard]: http://perf-dash.k8s.io/
|
||||
[readme]: https://github.com/kubernetes/community/tree/master/sig-scheduling
|
||||
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ The Chairs of the SIG run operations and processes governing the SIG.
|
|||
- GitHub Teams:
|
||||
- [@kubernetes/sig-security-leads](https://github.com/orgs/kubernetes/teams/sig-security-leads) - SIG Security Leads
|
||||
- [@kubernetes/sig-security-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-security-pr-reviews) - SIG Security PR review notifications
|
||||
- Steering Committee Liaison: Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**)
|
||||
- Steering Committee Liaison: Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**)
|
||||
|
||||
## Working Groups
|
||||
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
|
|||
- [@kubernetes/sig-storage-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-storage-pr-reviews) - PR Reviews
|
||||
- [@kubernetes/sig-storage-proposals](https://github.com/orgs/kubernetes/teams/sig-storage-proposals) - Design Proposals
|
||||
- [@kubernetes/sig-storage-test-failures](https://github.com/orgs/kubernetes/teams/sig-storage-test-failures) - Test Failures and Triage
|
||||
- Steering Committee Liaison: Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**)
|
||||
- Steering Committee Liaison: Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**)
|
||||
|
||||
## Working Groups
|
||||
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
|
|||
- GitHub Teams:
|
||||
- [@kubernetes/sig-testing](https://github.com/orgs/kubernetes/teams/sig-testing) - General Discussion
|
||||
- [@kubernetes/sig-testing-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-testing-pr-reviews) - PR Reviews
|
||||
- Steering Committee Liaison: Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**)
|
||||
- Steering Committee Liaison: Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**)
|
||||
|
||||
## Working Groups
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ The Chairs of the SIG run operations and processes governing the SIG.
|
|||
- Slack: [#sig-ui](https://kubernetes.slack.com/messages/sig-ui)
|
||||
- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-ui)
|
||||
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fui)
|
||||
- Steering Committee Liaison: Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**)
|
||||
- Steering Committee Liaison: Maciej Szulik (**[@soltysh](https://github.com/soltysh)**)
|
||||
|
||||
## Subprojects
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ The [charter](charter.md) defines the scope and governance of the Windows Specia
|
|||
### Chairs
|
||||
The Chairs of the SIG run operations and processes governing the SIG.
|
||||
|
||||
* Aravindh Puthiyaparambil (**[@aravindhp](https://github.com/aravindhp)**), Redhat
|
||||
* Aravindh Puthiyaparambil (**[@aravindhp](https://github.com/aravindhp)**), Red Hat
|
||||
* Mark Rossetti (**[@marosset](https://github.com/marosset)**), Microsoft
|
||||
|
||||
### Technical Leads
|
||||
|
|
|
|||
354
sigs.yaml
354
sigs.yaml
|
|
@ -25,12 +25,13 @@ sigs:
|
|||
name: Joe Betz
|
||||
company: Google
|
||||
meetings:
|
||||
- description: Kubebuilder and Controller Runtime Meeting
|
||||
- description: Kubebuilder Meeting
|
||||
day: Thursday
|
||||
time: "11:00"
|
||||
tz: PT (Pacific Time)
|
||||
frequency: biweekly
|
||||
archive_url: https://docs.google.com/document/d/1Ih-2cgg1bUrLwLVTB9tADlPcVdgnuMNBGbUl4D-0TIk/edit?usp=sharing
|
||||
archive_url: https://docs.google.com/document/d/1GbSkHAxIaFTm2fL92z3WeWrCtnIjXfr7gNZSySLHhmk/edit?usp=sharing
|
||||
recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP0SOaFeA9f3dwdCNECEKkX3
|
||||
- description: Regular SIG Meeting
|
||||
day: Wednesday
|
||||
time: "11:00"
|
||||
|
|
@ -278,7 +279,7 @@ sigs:
|
|||
company: Red Hat
|
||||
- github: dims
|
||||
name: Davanum Srinivas
|
||||
company: Amazon Web Services
|
||||
company: Amazon
|
||||
- github: johnbelamaric
|
||||
name: John Belamaric
|
||||
company: Google
|
||||
|
|
@ -413,12 +414,12 @@ sigs:
|
|||
- github: deads2k
|
||||
name: David Eads
|
||||
company: Red Hat
|
||||
- github: enj
|
||||
name: Mo Khan
|
||||
company: Microsoft
|
||||
- github: liggitt
|
||||
name: Jordan Liggitt
|
||||
company: Google
|
||||
- github: mikedanese
|
||||
name: Mike Danese
|
||||
company: Google
|
||||
emeritus_leads:
|
||||
- github: ericchiang
|
||||
name: Eric Chiang
|
||||
|
|
@ -437,7 +438,7 @@ sigs:
|
|||
recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP0VMOZ-V7-5AchXTHAQFzJw
|
||||
- description: Secrets Store CSI Meeting
|
||||
day: Thursday
|
||||
time: "8:00"
|
||||
time: "9:00"
|
||||
tz: PT (Pacific Time)
|
||||
frequency: biweekly
|
||||
url: https://zoom.us/j/91272289538
|
||||
|
|
@ -468,8 +469,8 @@ sigs:
|
|||
- name: sig-auth-test-failures
|
||||
description: Test Failures and Triage
|
||||
liaison:
|
||||
github: cblecker
|
||||
name: Christoph Blecker
|
||||
github: pohly
|
||||
name: Patrick Ohly
|
||||
subprojects:
|
||||
- name: audit-logging
|
||||
description: |
|
||||
|
|
@ -603,7 +604,7 @@ sigs:
|
|||
time: "16:00"
|
||||
tz: Poland
|
||||
frequency: weekly
|
||||
url: https://zoom.us/j/944410904
|
||||
url: https://zoom.us/j/96548204174
|
||||
archive_url: https://docs.google.com/document/d/1RvhQAEIrVLHbyNnuaT99-6u9ZUMp7BfkPupT2LAZK7w/edit
|
||||
contact:
|
||||
slack: sig-autoscaling
|
||||
|
|
@ -624,25 +625,25 @@ sigs:
|
|||
- name: sig-autoscaling-test-failures
|
||||
description: Test Failures and Triage
|
||||
liaison:
|
||||
github: tpepper
|
||||
name: Tim Pepper
|
||||
github: soltysh
|
||||
name: Maciej Szulik
|
||||
subprojects:
|
||||
- name: addon-resizer
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes/autoscaler/master/addon-resizer/OWNERS
|
||||
- name: cluster-autoscaler
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes/autoscaler/master/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes/autoscaler/master/cluster-autoscaler/OWNERS
|
||||
- name: horizontal-pod-autoscaler
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes/api/master/autoscaling/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/controller/podautoscaler/OWNERS
|
||||
- name: scale-client
|
||||
- name: karpenter
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes/client-go/master/scale/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/karpenter/main/OWNERS
|
||||
- name: vertical-pod-autoscaler
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes/autoscaler/master/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes/autoscaler/master/vertical-pod-autoscaler/OWNERS
|
||||
- dir: sig-cli
|
||||
name: CLI
|
||||
mission_statement: >
|
||||
|
|
@ -737,8 +738,8 @@ sigs:
|
|||
- name: sig-cli-test-failures
|
||||
description: Test Failures and Triage
|
||||
liaison:
|
||||
github: justaugustus
|
||||
name: Stephen Augustus
|
||||
github: pacoxu
|
||||
name: Paco Xu 徐俊杰
|
||||
subprojects:
|
||||
- name: cli-experimental
|
||||
owners:
|
||||
|
|
@ -848,12 +849,13 @@ sigs:
|
|||
- name: sig-cloud-providers-misc
|
||||
description: General Discussion
|
||||
liaison:
|
||||
github: justaugustus
|
||||
name: Stephen Augustus
|
||||
github: soltysh
|
||||
name: Maciej Szulik
|
||||
subprojects:
|
||||
- name: cloud-provider-extraction-migration
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/apiserver-network-proxy/master/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/cloud-pv-admission-labeler/main/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes/community/master/sig-cloud-provider/cloud-provider-extraction-migration/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes/legacy-cloud-providers/master/OWNERS
|
||||
meetings:
|
||||
|
|
@ -903,7 +905,7 @@ sigs:
|
|||
time: "9:00"
|
||||
tz: PT (Pacific Time)
|
||||
frequency: 'biweekly 2019 start date: Jan. 11th'
|
||||
url: https://zoom.us/my/k8ssigaws
|
||||
url: https://zoom.us/j/508079177?pwd=ZmEvMksxdTFTc0N1eXFLRm91QUlyUT09
|
||||
archive_url: https://docs.google.com/document/d/1-i0xQidlXnFEP9fXHWkBxqySkXwJnrGJP9OGyP2_P14/edit
|
||||
recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP29DzPOBBaJi-SO3AQ_b4HC
|
||||
- name: provider-azure
|
||||
|
|
@ -1069,6 +1071,7 @@ sigs:
|
|||
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/cluster-api/main/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/logical-cluster/main/OWNERS
|
||||
meetings:
|
||||
- description: Cluster API office hours
|
||||
day: Wednesday
|
||||
|
|
@ -1081,6 +1084,9 @@ sigs:
|
|||
- name: cluster-api-addon-provider-helm
|
||||
description: Implementation of Cluster Add-on Provider for Helm, an add-on orchestration
|
||||
solution for Cluster API using Helm.
|
||||
contact:
|
||||
slack: cluster-api-addon-helm
|
||||
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle
|
||||
owners:
|
||||
- https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/blob/main/OWNERS
|
||||
- name: cluster-api-ipam-provider-in-cluster
|
||||
|
|
@ -1327,12 +1333,6 @@ sigs:
|
|||
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/kubespray/master/OWNERS
|
||||
- name: logical-cluster
|
||||
description: A set of APIs to improve the Kubernetes user experience for cluster
|
||||
administration by offering utilities to interact with fleet of clusters which
|
||||
can be managed by Cluster API, or other entities (like cloud providers).
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/logical-cluster/main/OWNERS
|
||||
- name: minikube
|
||||
description: Implements a local Kubernetes cluster for application development
|
||||
on macOS, Linux, and Windows
|
||||
|
|
@ -1363,15 +1363,9 @@ sigs:
|
|||
label: contributor-experience
|
||||
leadership:
|
||||
chairs:
|
||||
- github: jberkus
|
||||
name: Josh Berkus
|
||||
company: Red Hat
|
||||
- github: kaslin
|
||||
name: Kaslin Fields
|
||||
company: Google
|
||||
- github: mrbobbytables
|
||||
name: Bob Killen
|
||||
company: Google
|
||||
- github: palnabarun
|
||||
name: Nabarun Pal
|
||||
company: VMware
|
||||
|
|
@ -1382,12 +1376,6 @@ sigs:
|
|||
- github: Priyankasaggu11929
|
||||
name: Priyanka Saggu
|
||||
company: SUSE
|
||||
- github: cblecker
|
||||
name: Christoph Blecker
|
||||
company: Red Hat
|
||||
- github: nikhita
|
||||
name: Nikhita Raghunath
|
||||
company: VMware
|
||||
emeritus_leads:
|
||||
- github: Phillels
|
||||
name: Elsie Phillips
|
||||
|
|
@ -1395,8 +1383,16 @@ sigs:
|
|||
name: Alison Dowdney
|
||||
- github: castrojo
|
||||
name: Jorge Castro
|
||||
- github: cblecker
|
||||
name: Christoph Blecker
|
||||
- github: grodrigues3
|
||||
name: Garrett Rodrigues
|
||||
- github: jberkus
|
||||
name: Josh Berkus
|
||||
- github: mrbobbytables
|
||||
name: Bob Killen
|
||||
- github: nikhita
|
||||
name: Nikhita Raghunath
|
||||
- github: parispittman
|
||||
name: Paris Pittman
|
||||
meetings:
|
||||
|
|
@ -1437,7 +1433,6 @@ sigs:
|
|||
description: |
|
||||
Contributor Communications focuses on amplifying the success of Kubernetes contributors through marketing.
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/contributor-tweets/master/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/lwkd/main/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes/community/master/communication/contributor-comms/OWNERS
|
||||
meetings:
|
||||
|
|
@ -1531,7 +1526,7 @@ sigs:
|
|||
company: SUSE
|
||||
- github: natalisucks
|
||||
name: Natali Vlatko
|
||||
company: Wayfair
|
||||
company: Cisco
|
||||
- github: reylejano
|
||||
name: Rey Lejano
|
||||
company: SUSE
|
||||
|
|
@ -1541,7 +1536,7 @@ sigs:
|
|||
company: Independent
|
||||
- github: onlydole
|
||||
name: Taylor Dolezal
|
||||
company: Independent
|
||||
company: CNCF
|
||||
- github: sftim
|
||||
name: Tim Bannister
|
||||
company: The Scale Factory
|
||||
|
|
@ -1600,7 +1595,7 @@ sigs:
|
|||
day: Tuesday
|
||||
time: "17:30"
|
||||
tz: UTC
|
||||
frequency: weekly - except fourth Tuesday every month
|
||||
frequency: biweekly
|
||||
url: https://docs.google.com/document/d/1emuO4nmaQq3K8JZ9-MQeIygtrCPO9kWv7U7RzTaW4F8/edit
|
||||
archive_url: https://docs.google.com/document/d/1emuO4nmaQq3K8JZ9-MQeIygtrCPO9kWv7U7RzTaW4F8/edit
|
||||
recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP3b5hlx0YV7Lo7DtckM84y8
|
||||
|
|
@ -1651,8 +1646,8 @@ sigs:
|
|||
- name: sig-docs-zh-owners
|
||||
description: Chinese language content
|
||||
liaison:
|
||||
github: cpanato
|
||||
name: Carlos Tadeu Panato Jr.
|
||||
github: justaugustus
|
||||
name: Stephen Augustus
|
||||
subprojects:
|
||||
- name: kubernetes-blog
|
||||
owners:
|
||||
|
|
@ -1666,6 +1661,120 @@ sigs:
|
|||
- name: website
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes/website/master/OWNERS
|
||||
- dir: sig-etcd
|
||||
name: etcd
|
||||
mission_statement: >
|
||||
etcd is a production-ready store for building cloud-native distributed systems
|
||||
and managing cloud-native infrastructure via orchestrators like Kubernetes.
|
||||
|
||||
Etcd should provide distributed system primitives** (such as distributed locking
|
||||
and leader election) that allow users to **create scalable, highly available and
|
||||
fault-tolerant systems.
|
||||
|
||||
Etcd is the place to store the infrastructure configuration, not only as part
|
||||
of Kubernetes, but also as a standalone solution.
|
||||
|
||||
charter_link: charter.md
|
||||
label: etcd
|
||||
leadership:
|
||||
chairs:
|
||||
- github: jmhbnz
|
||||
name: James Blair
|
||||
company: Red Hat
|
||||
- github: wenjiaswe
|
||||
name: Wenjia Zhang
|
||||
company: Google
|
||||
tech_leads:
|
||||
- github: ahrtr
|
||||
name: Benjamin Wang
|
||||
company: VMWare
|
||||
- github: serathius
|
||||
name: Marek Siarkowicz
|
||||
company: Google
|
||||
meetings:
|
||||
- description: Regular SIG Meeting
|
||||
day: Thursday
|
||||
time: "11:00"
|
||||
tz: PT (Pacific Time)
|
||||
frequency: biweekly
|
||||
url: https://zoom.us/my/cncfetcdproject
|
||||
archive_url: https://docs.google.com/document/d/16XEGyPBisZvmmoIHSZzv__LoyOeluC5a4x353CX0SIM/edit?usp=sharing
|
||||
recordings_url: https://www.youtube.com/playlist?list=PLRGL688DpO9rtufHbiunuCHddYY6MGkwW
|
||||
contact:
|
||||
slack: etcd
|
||||
mailing_list: https://groups.google.com/g/etcd-dev
|
||||
teams:
|
||||
- name: sig-etcd-leads
|
||||
description: SIG Chairs and Tech Leads
|
||||
liaison:
|
||||
github: mrbobbytables
|
||||
name: Bob Killen
|
||||
subprojects:
|
||||
- name: bbolt
|
||||
description: An embedded key/value database for Go.
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/bbolt/master/MAINTAINERS
|
||||
- name: cetcd
|
||||
description: Serve Consul with etcd
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/cetcd/master/MAINTAINERS
|
||||
- name: dbtester
|
||||
description: Distributed database benchmark tester
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/dbtester/master/MAINTAINERS
|
||||
- name: discovery.etcd.io
|
||||
description: Kubernetes manifests powering discovery.etcd.io
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/discovery.etcd.io/master/MAINTAINERS
|
||||
- name: discoveryserver
|
||||
description: Public etcd Discovery Service
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/discoveryserver/master/MAINTAINERS
|
||||
- name: etcd
|
||||
description: Distributed reliable key-value store for the most critical data of
|
||||
a distributed system
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/etcd/master/MAINTAINERS
|
||||
- name: etcd-play
|
||||
description: etcd playground
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/etcd-play/master/MAINTAINERS
|
||||
- name: etcdlabs
|
||||
description: etcd playground
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/etcdlabs/master/MAINTAINERS
|
||||
- name: gofail
|
||||
description: failpoints for go
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/gofail/master/MAINTAINERS
|
||||
- name: govanityurls
|
||||
description: Use a custom domain in your Go import path
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/govanityurls/master/MAINTAINERS
|
||||
- name: jetcd
|
||||
description: etcd java client
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/jetcd/master/MAINTAINERS
|
||||
- name: maintainers
|
||||
description: issue tracking for project wide non-code concerns
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/maintainers/master/MAINTAINERS
|
||||
- name: protodoc
|
||||
description: protodoc generates Protocol Buffer documentation.
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/protodoc/master/MAINTAINERS
|
||||
- name: raft
|
||||
description: Raft library for maintaining a replicated state machine
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/raft/master/MAINTAINERS
|
||||
- name: website
|
||||
description: etcd-io
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/website/master/MAINTAINERS
|
||||
- name: zetcd
|
||||
description: Serve the Apache Zookeeper API but back it with an etcd cluster
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/etcd-io/zetcd/master/MAINTAINERS
|
||||
- dir: sig-instrumentation
|
||||
name: Instrumentation
|
||||
mission_statement: >
|
||||
|
|
@ -1722,8 +1831,8 @@ sigs:
|
|||
- name: sig-instrumentation-members
|
||||
description: SIG Membership Roster
|
||||
liaison:
|
||||
github: cblecker
|
||||
name: Christoph Blecker
|
||||
github: pohly
|
||||
name: Patrick Ohly
|
||||
subprojects:
|
||||
- name: custom-metrics-apiserver
|
||||
owners:
|
||||
|
|
@ -1788,17 +1897,24 @@ sigs:
|
|||
company: VMware
|
||||
- github: dims
|
||||
name: Davanum Srinivas
|
||||
company: Amazon Web Services
|
||||
company: Amazon
|
||||
tech_leads:
|
||||
- github: spiffxp
|
||||
name: Aaron Crickenberger
|
||||
company: Google
|
||||
- github: thockin
|
||||
name: Tim Hockin
|
||||
- github: BenTheElder
|
||||
name: Benjamin Elder
|
||||
company: Google
|
||||
- github: ameukam
|
||||
name: Arnaud Meukam
|
||||
company: VMware
|
||||
- github: upodroid
|
||||
name: Mahamed Ali
|
||||
company: Cisco
|
||||
emeritus_leads:
|
||||
- github: bartsmykla
|
||||
name: Bart Smykla
|
||||
- github: spiffxp
|
||||
name: Aaron Crickenberger
|
||||
- github: thockin
|
||||
name: Tim Hockin
|
||||
meetings:
|
||||
- description: Regular SIG Meeting
|
||||
day: Wednesday
|
||||
|
|
@ -1975,6 +2091,9 @@ sigs:
|
|||
- name: about-api
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/about-api/master/OWNERS
|
||||
- name: cluster-inventory-api
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/cluster-inventory-api/main/OWNERS
|
||||
- name: mcs-api
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/mcs-api/master/OWNERS
|
||||
|
|
@ -2002,18 +2121,19 @@ sigs:
|
|||
- github: thockin
|
||||
name: Tim Hockin
|
||||
company: Google
|
||||
tech_leads:
|
||||
- github: danwinship
|
||||
name: Dan Winship
|
||||
company: Red Hat
|
||||
- github: thockin
|
||||
name: Tim Hockin
|
||||
company: Google
|
||||
emeritus_leads:
|
||||
- github: caseydavenport
|
||||
name: Casey Davenport
|
||||
- github: dcbw
|
||||
name: Dan Williams
|
||||
meetings:
|
||||
- description: Gateway API Code Jam
|
||||
day: Friday
|
||||
time: "08:30"
|
||||
tz: PT (Pacific Time)
|
||||
frequency: Last Friday of the Month
|
||||
url: https://zoom.us/j/96900767253
|
||||
- description: Gateway API GAMMA Meeting (APAC Friendly)
|
||||
day: Tuesday
|
||||
time: "15:00"
|
||||
|
|
@ -2050,18 +2170,6 @@ sigs:
|
|||
url: https://zoom.us/j/98377891310
|
||||
archive_url: https://docs.google.com/document/d/1DKlpcV6DAW0DsBrzh-OLkZvJQmABCVfRIRWBWjc4zOs/edit
|
||||
recordings_url: https://www.youtube.com/watch?v=VkbEihIb7tA&list=PL69nYSiGNLP2Rqe8T4mDnyHqDZ4VYPY1X
|
||||
- description: SIG Network KPNG APAC Meeting
|
||||
day: Wednesday
|
||||
time: "16:00"
|
||||
tz: IST (Indian Standard Time)
|
||||
frequency: weekly
|
||||
url: https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit
|
||||
- description: SIG Network KPNG Meeting
|
||||
day: Friday
|
||||
time: "7:30"
|
||||
tz: PT (Pacific Time)
|
||||
frequency: weekly
|
||||
url: https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit
|
||||
- description: SIG Network Meeting
|
||||
day: Thursday
|
||||
time: "09:00"
|
||||
|
|
@ -2078,6 +2186,12 @@ sigs:
|
|||
url: https://zoom.us/j/95680858961?pwd=M1c2TTdMZHpMUUtIYXRpbjRobkNJZz09
|
||||
archive_url: https://docs.google.com/document/d/1pe_0aOsI35BEsQJ-FhFH9Z_pWQcU2uqwAnOx2NIx6OY/edit
|
||||
recordings_url: https://www.youtube.com/watch?v=phCA5-vWkVM&list=PL69nYSiGNLP2E8vmnqo5MwPOY25sDWIxb
|
||||
- description: Sig-Network Code Jam
|
||||
day: Friday
|
||||
time: "08:30"
|
||||
tz: PT (Pacific Time)
|
||||
frequency: Last Friday of the Month
|
||||
url: https://zoom.us/j/96900767253
|
||||
contact:
|
||||
slack: sig-network
|
||||
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-network
|
||||
|
|
@ -2097,8 +2211,8 @@ sigs:
|
|||
- name: sig-network-test-failures
|
||||
description: Test Failures and Triage
|
||||
liaison:
|
||||
github: tpepper
|
||||
name: Tim Pepper
|
||||
github: soltysh
|
||||
name: Maciej Szulik
|
||||
subprojects:
|
||||
- name: cluster-proportional-autoscaler
|
||||
owners:
|
||||
|
|
@ -2115,6 +2229,7 @@ sigs:
|
|||
contact:
|
||||
slack: sig-network-gateway-api
|
||||
owners:
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/blixt/main/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/gateway-api/master/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes-sigs/ingress2gateway/main/OWNERS
|
||||
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/controller/endpoint/OWNERS
|
||||
|
|
@ -2203,8 +2318,8 @@ sigs:
|
|||
- name: sig-node-test-failures
|
||||
description: Test Failures and Triage
|
||||
liaison:
|
||||
github: tpepper
|
||||
name: Tim Pepper
|
||||
github: pacoxu
|
||||
name: Paco Xu 徐俊杰
|
||||
subprojects:
|
||||
- name: ci-testing
|
||||
contact:
|
||||
|
|
@ -2419,10 +2534,10 @@ sigs:
|
|||
chairs:
|
||||
- github: marseel
|
||||
name: Marcel Zieba
|
||||
company: Google
|
||||
company: Isovalent
|
||||
- github: shyamjvs
|
||||
name: Shyam Jeedigunta
|
||||
company: AWS
|
||||
company: Amazon
|
||||
tech_leads:
|
||||
- github: wojtek-t
|
||||
name: Wojciech Tyczynski
|
||||
|
|
@ -2625,8 +2740,8 @@ sigs:
|
|||
- name: sig-security-pr-reviews
|
||||
description: SIG Security PR review notifications
|
||||
liaison:
|
||||
github: cpanato
|
||||
name: Carlos Tadeu Panato Jr.
|
||||
github: justaugustus
|
||||
name: Stephen Augustus
|
||||
subprojects:
|
||||
- name: security-assessments
|
||||
description: Security self assessments for upstream projects
|
||||
|
|
@ -2722,8 +2837,8 @@ sigs:
|
|||
- name: sig-storage-test-failures
|
||||
description: Test Failures and Triage
|
||||
liaison:
|
||||
github: cpanato
|
||||
name: Carlos Tadeu Panato Jr.
|
||||
github: pacoxu
|
||||
name: Paco Xu 徐俊杰
|
||||
subprojects:
|
||||
- name: external-storage
|
||||
owners:
|
||||
|
|
@ -2849,8 +2964,8 @@ sigs:
|
|||
- name: sig-testing-pr-reviews
|
||||
description: PR Reviews
|
||||
liaison:
|
||||
github: cpanato
|
||||
name: Carlos Tadeu Panato Jr.
|
||||
github: pacoxu
|
||||
name: Paco Xu 徐俊杰
|
||||
subprojects:
|
||||
- name: Cloud Provider for KIND
|
||||
description: |
|
||||
|
|
@ -2944,8 +3059,8 @@ sigs:
|
|||
slack: sig-ui
|
||||
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-ui
|
||||
liaison:
|
||||
github: justaugustus
|
||||
name: Stephen Augustus
|
||||
github: soltysh
|
||||
name: Maciej Szulik
|
||||
subprojects:
|
||||
- name: dashboard
|
||||
owners:
|
||||
|
|
@ -2962,7 +3077,7 @@ sigs:
|
|||
chairs:
|
||||
- github: aravindhp
|
||||
name: Aravindh Puthiyaparambil
|
||||
company: Redhat
|
||||
company: Red Hat
|
||||
- github: marosset
|
||||
name: Mark Rossetti
|
||||
company: Microsoft
|
||||
|
|
@ -3098,18 +3213,21 @@ workinggroups:
|
|||
- github: Huang-Wei
|
||||
name: Wei Huang
|
||||
company: Apple
|
||||
- github: ahg-g
|
||||
name: Abdullah Gharaibeh
|
||||
company: Google
|
||||
- github: endocrimes
|
||||
name: Danielle Lancashire
|
||||
company: Independent
|
||||
- github: mwielgus
|
||||
name: Marcin Wielgus
|
||||
company: Google
|
||||
- github: soltysh
|
||||
name: Maciej Szulik
|
||||
company: Red Hat
|
||||
- github: swatisehgal
|
||||
name: Swati Sehgal
|
||||
company: Red Hat
|
||||
emeritus_leads:
|
||||
- github: ahg-g
|
||||
name: Abdullah Gharaibeh
|
||||
meetings:
|
||||
- description: Regular Meeting ([Calendar](https://calendar.google.com/calendar/embed?src=8ulop9k0jfpuo0t7kp8d9ubtj4%40group.calendar.google.com))
|
||||
day: Thursdays (starting March 3rd 2022)
|
||||
|
|
@ -3163,8 +3281,8 @@ workinggroups:
|
|||
slack: wg-data-protection
|
||||
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-data-protection
|
||||
liaison:
|
||||
github: cblecker
|
||||
name: Christoph Blecker
|
||||
github: pohly
|
||||
name: Patrick Ohly
|
||||
- dir: wg-iot-edge
|
||||
name: IoT Edge
|
||||
mission_statement: >
|
||||
|
|
@ -3208,8 +3326,8 @@ workinggroups:
|
|||
slack: wg-iot-edge
|
||||
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-wg-iot-edge
|
||||
liaison:
|
||||
github: cblecker
|
||||
name: Christoph Blecker
|
||||
github: pohly
|
||||
name: Patrick Ohly
|
||||
- dir: wg-lts
|
||||
name: LTS
|
||||
mission_statement: >
|
||||
|
|
@ -3246,7 +3364,7 @@ workinggroups:
|
|||
tz: PT (Pacific Time)
|
||||
frequency: biweekly
|
||||
url: https://zoom.us/j/92480197536?pwd=dmtSMGJRQmNYYTIyZkFlQ25JRngrdz09
|
||||
archive_url: TBD
|
||||
archive_url: https://docs.google.com/document/d/1RI_EL35MwQxrHqlWvtQNINhOSWergL3hmOSgC5PeZss/edit
|
||||
recordings_url: TBD
|
||||
contact:
|
||||
slack: wg-lts
|
||||
|
|
@ -3291,8 +3409,8 @@ workinggroups:
|
|||
slack: wg-policy
|
||||
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-wg-policy
|
||||
liaison:
|
||||
github: cblecker
|
||||
name: Christoph Blecker
|
||||
github: pohly
|
||||
name: Patrick Ohly
|
||||
- dir: wg-structured-logging
|
||||
name: Structured Logging
|
||||
mission_statement: >
|
||||
|
|
@ -3312,21 +3430,13 @@ workinggroups:
|
|||
label: structured-logging
|
||||
leadership:
|
||||
chairs:
|
||||
- github: mengjiao-liu
|
||||
name: Mengjiao Liu
|
||||
company: DaoCloud
|
||||
- github: pohly
|
||||
name: Patrick Ohly
|
||||
company: Intel
|
||||
- github: serathius
|
||||
name: Marek Siarkowicz
|
||||
company: Google
|
||||
meetings:
|
||||
- description: Regular Meeting
|
||||
day: Thursday
|
||||
time: "15:30"
|
||||
tz: London-UK
|
||||
frequency: biweekly
|
||||
url: https://zoom.us/j/96716142646?pwd=VmgrN29sbmhDREp3R0NtZlpGSlZ4Zz09
|
||||
archive_url: https://docs.google.com/document/d/1R9bZ34L9vR1ftH0dFeOp-j50lLh5ijKVwwXJ3LDrY4I/edit?usp=sharing
|
||||
recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP2GY3so1z2Cnkvkt5A_x1Aw
|
||||
meetings: []
|
||||
contact:
|
||||
slack: wg-structured-logging
|
||||
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging
|
||||
|
|
@ -3353,7 +3463,7 @@ committees:
|
|||
company: Independent
|
||||
- github: hlipsig
|
||||
name: Hilliary Lipsig
|
||||
company: RedHat
|
||||
company: Red Hat
|
||||
- github: jeremyrickard
|
||||
name: Jeremy Rickard
|
||||
company: Microsoft
|
||||
|
|
@ -3397,8 +3507,8 @@ committees:
|
|||
- name: code-of-conduct-committee
|
||||
description: General Discussion
|
||||
liaison:
|
||||
github: tpepper
|
||||
name: Tim Pepper
|
||||
github: palnabarun
|
||||
name: Nabarun Pal
|
||||
- dir: committee-security-response
|
||||
name: Security Response
|
||||
mission_statement: >
|
||||
|
|
@ -3468,24 +3578,24 @@ committees:
|
|||
- github: BenTheElder
|
||||
name: Benjamin Elder
|
||||
company: Google
|
||||
- github: cblecker
|
||||
name: Christoph Blecker
|
||||
company: Red Hat
|
||||
- github: cpanato
|
||||
name: Carlos Tadeu Panato Jr.
|
||||
company: Chainguard, Inc
|
||||
- github: justaugustus
|
||||
name: Stephen Augustus
|
||||
company: Cisco
|
||||
- github: mrbobbytables
|
||||
name: Bob Killen
|
||||
company: Google
|
||||
- github: pacoxu
|
||||
name: Paco Xu 徐俊杰
|
||||
company: DaoCloud
|
||||
- github: palnabarun
|
||||
name: Nabarun Pal
|
||||
company: VMware
|
||||
- github: tpepper
|
||||
name: Tim Pepper
|
||||
company: VMware
|
||||
- github: pohly
|
||||
name: Patrick Ohly
|
||||
company: Intel
|
||||
- github: soltysh
|
||||
name: Maciej Szulik
|
||||
company: Red Hat
|
||||
meetings:
|
||||
- description: Private Steering Committee Meeting
|
||||
day: third Monday
|
||||
|
|
@ -3495,8 +3605,8 @@ committees:
|
|||
url: https://bit.ly/k8s-steering-wd
|
||||
recordings_url: https://www.youtube.com/watch?v=YAzgJRQxsdc&list=PL69nYSiGNLP1yP1B_nd9-drjoxp0Q14qM
|
||||
- description: Public Steering Committee Meeting
|
||||
day: first Monday
|
||||
time: "9:30"
|
||||
day: first Wednesday
|
||||
time: "8:00"
|
||||
tz: PT (Pacific Time)
|
||||
frequency: monthly
|
||||
url: https://bit.ly/k8s-steering-wd
|
||||
|
|
|
|||
|
|
@ -27,11 +27,15 @@ The [charter](charter.md) defines the scope and governance of the Batch Working
|
|||
## Organizers
|
||||
|
||||
* Wei Huang (**[@Huang-Wei](https://github.com/Huang-Wei)**), Apple
|
||||
* Abdullah Gharaibeh (**[@ahg-g](https://github.com/ahg-g)**), Google
|
||||
* Danielle Lancashire (**[@endocrimes](https://github.com/endocrimes)**), Independent
|
||||
* Marcin Wielgus (**[@mwielgus](https://github.com/mwielgus)**), Google
|
||||
* Maciej Szulik (**[@soltysh](https://github.com/soltysh)**), Red Hat
|
||||
* Swati Sehgal (**[@swatisehgal](https://github.com/swatisehgal)**), Red Hat
|
||||
|
||||
## Emeritus Organizers
|
||||
|
||||
* Abdullah Gharaibeh (**[@ahg-g](https://github.com/ahg-g)**)
|
||||
|
||||
## Contact
|
||||
- Slack: [#wg-batch](https://kubernetes.slack.com/messages/wg-batch)
|
||||
- [Mailing list](https://groups.google.com/a/kubernetes.io/g/wg-batch)
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ The [charter](charter.md) defines the scope and governance of the Data Protectio
|
|||
- Slack: [#wg-data-protection](https://kubernetes.slack.com/messages/wg-data-protection)
|
||||
- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-data-protection)
|
||||
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fdata-protection)
|
||||
- Steering Committee Liaison: Christoph Blecker (**[@cblecker](https://github.com/cblecker)**)
|
||||
- Steering Committee Liaison: Patrick Ohly (**[@pohly](https://github.com/pohly)**)
|
||||
<!-- BEGIN CUSTOM CONTENT -->
|
||||
|
||||
<!-- END CUSTOM CONTENT -->
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ A Working Group dedicated to discussing, designing and documenting using Kuberne
|
|||
- Slack: [#wg-iot-edge](https://kubernetes.slack.com/messages/wg-iot-edge)
|
||||
- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-iot-edge)
|
||||
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fiot-edge)
|
||||
- Steering Committee Liaison: Christoph Blecker (**[@cblecker](https://github.com/cblecker)**)
|
||||
- Steering Committee Liaison: Patrick Ohly (**[@pohly](https://github.com/pohly)**)
|
||||
<!-- BEGIN CUSTOM CONTENT -->
|
||||
This working group is a cross-SIG effort currently sponsored by _sig-networking_ and _sig-multicluster_ with
|
||||
a focus on improving Kubernetes IoT and Edge deployments. Community members are encouraged to share their ideas in this working group to reach broad consensus across the SIGs. Once consensus is reached, the enhancements
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ The working group is organized with the goal of developing a better understandin
|
|||
## Meetings
|
||||
*Joining the [mailing list](https://groups.google.com/a/kubernetes.io/g/wg-lts) for the group will typically add invites for the following meetings to your calendar.*
|
||||
* Regular WG Meeting: [Tuesdays at 07:00 PT (Pacific Time)](https://zoom.us/j/92480197536?pwd=dmtSMGJRQmNYYTIyZkFlQ25JRngrdz09) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=07:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](TBD).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1RI_EL35MwQxrHqlWvtQNINhOSWergL3hmOSgC5PeZss/edit).
|
||||
* [Meeting recordings](TBD).
|
||||
|
||||
## Organizers
|
||||
|
|
|
|||
|
|
@ -1,43 +0,0 @@
|
|||
<!---
|
||||
This is an autogenerated file!
|
||||
|
||||
Please do not edit this file directly, but instead make changes to the
|
||||
sigs.yaml file in the project root.
|
||||
|
||||
To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
|
||||
--->
|
||||
# Multitenancy Working Group
|
||||
|
||||
Define the models of multitenancy that Kubernetes will support. Discuss and execute upon any remaining work that needs to be done to support these models. Create conformance tests that will prove that these models can be built and used in production environments.
|
||||
|
||||
## Stakeholder SIGs
|
||||
* [SIG API Machinery](/sig-api-machinery)
|
||||
* [SIG Auth](/sig-auth)
|
||||
* [SIG Network](/sig-network)
|
||||
* [SIG Node](/sig-node)
|
||||
* [SIG Scheduling](/sig-scheduling)
|
||||
* [SIG Storage](/sig-storage)
|
||||
|
||||
## Meetings
|
||||
*Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-multitenancy) for the group will typically add invites for the following meetings to your calendar.*
|
||||
* Regular WG Meeting: [Tuesdays at 11:00 PT (Pacific Time)](https://zoom.us/my/k8s.sig.auth) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=11:00&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](https://docs.google.com/document/d/1fj3yzmeU2eU8ZNBCUJG97dk_wC7228-e_MmdcmTNrZY/edit?usp=sharing).
|
||||
* [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP1tBA0W8zEe6UwPsabGQk-j).
|
||||
|
||||
## Organizers
|
||||
|
||||
* Sanjeev Rampal (**[@srampal](https://github.com/srampal)**), Cisco
|
||||
* Tasha Drew (**[@tashimi](https://github.com/tashimi)**), VMware
|
||||
|
||||
## Emeritus Organizers
|
||||
|
||||
* David Oppenheimer (**[@davidopp](https://github.com/davidopp)**)
|
||||
|
||||
## Contact
|
||||
- Slack: [#wg-multitenancy](https://kubernetes.slack.com/messages/wg-multitenancy)
|
||||
- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-multitenancy)
|
||||
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fmultitenancy)
|
||||
- Steering Committee Liaison: Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**)
|
||||
<!-- BEGIN CUSTOM CONTENT -->
|
||||
|
||||
<!-- END CUSTOM CONTENT -->
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue