Kubernetes Community Documentation
Welcome to the Kubernetes community documentation. Here you can learn about what's happening in the community.
Kubernetes uses Slack for community discussions.
Join : Joining is self service. Go to slack.k8s.io to join.
Access : Once you join, the team can be found at kubernetes.slack.io
Archives : Discussions on most channels are archived at kubernetes.slackarchive.io . Start archiving by inviting the slackarchive bot to a channel via /invite @slackarchive
To add new channels, contact one of the admins. Currently that includes briangrant, goltermann, jbeda, sarahnovotny and thockin.
Many important announcements and discussions end up on the main development group.
kubernetes-dev@googlegroups.com
Google Group
The weekly community meeting provides an opportunity for the different SIGs and other parts of the community to come together.
Much of the community activity is organized into a community meeting and numerous SIGs. Each of those groups operates a little differently which is reflected in how they capture notes, examples, and other information. Each groups material is in its subdirectory in this project.
The SIG meeting calendar is available as an [iCal to subscribe to] (https://calendar.google.com/calendar/ical/cgnt364vd8s86hr2phapfjc6uk%40group.calendar.google.com/public/basic.ics ) (simply copy and paste the url into any calendar product that supports the iCal format) or [html to view] (https://calendar.google.com/calendar/embed?src=cgnt364vd8s86hr2phapfjc6uk%40group.calendar.google.com&ctz=America/Los_Angeles ).
Name
Leads
Group
Slack Channel
Meetings
API Machinery @lavalamp (Daniel Smith, Google) https://github.com/orgs/kubernetes/people/deads2k )Group #sig-api-machinery Every other Wednesday at 11:00 AM PST
Apps @michelleN (Michelle Noorali, Deis) @mattfarina (Matt Farina, HPE) Group #sig-apps Weekly on Wednesday at 9:00 AM PST
Auth @ erictune (Eric Tune, Google) @ericchiang (Eric Chiang, CoreOS) https://github.com/orgs/kubernetes/people/liggitt ) https://github.com/orgs/kubernetes/people/deads2k )Group #sig-auth Biweekly Wednesdays at 1100 to 1200 PT
Autoscaling @fgrzadkowski (Filip Grządkowski, Google) Group #sig-autoscaling Biweekly (or triweekly) on Thurs at 0830 PT
AWS @justinsb (Justin Santa Barbara) @mfburnett (Mackenzie Burnett) Group #sig-aws TBD
Big Data @zmerlynn (Zach Loafman, Google) @timothysc (Timothy St. Clair, Red Hat) @wattsteve (Steve Watt, Red Hat) Group #sig-big-data Bi-weekly on Mondays at 1300 PT
Cluster Lifecycle [@lukemarsden (Luke Marsden, Weave)] (https://github.com/lukemarsden )
Group #sig-cluster-lifecycle Tuesdays at 09:00 AM PST on Zoom
Cluster Ops @zehicle (Rob Hirschfeld, RackN) https://github.com/mikedanese )Group #sig-cluster-ops Thursdays at 1:00 PM PST on hangouts
[Docs] (docs/README.md)
[@pwittrock (Philip Wittrock, Google)] (https://github.com/pwittrock ) https://github.com/johndmulhausen )
[Group] (https://groups.google.com/forum/#!forum/kubernetes-sig-docs )
[#sig-docs] (https://kubernetes.slack.com/messages/sig-docs )
TBD
Federation @quinton-hoole (Quinton Hoole, Google) Group #sig-federation ???
Network @thockin (Tim Hockin, Google) @dcbw (Dan Williams, Red Hat) @caseydavenport (Casey Davenport, Tigera) Group #sig-network Thursdays at 2:00 PM PST on Zoom
Node @dchen1107 (Dawn Chen, Google) @euank (Euan Kemp, CoreOS) @derekwaynecarr (Derek Carr, Red Hat) Group #sig-node Weekly on Tuesdays at 11:00 PT
OpenStack [@idvoretskyi (Ihor Dvoretskyi, Mirantis)] (https://github.com/idvoretskyi ) https://github.com/xsgordon )
Group #sig-openstack Every second Wednesday at 5 PM PDT / 2 PM EDT
Rktnetes [@euank (Euan Kemp, CoreOS)] (https://github.com/euank ) https://github.com/tmrts ) https://github.com/yifan-gu )
Group #rkt-runtime Weekly on Mondays at 13:00 PT
Scalability @lavalamp (Daniel Smith, Google) @countspongebob (Bob Wise, Samsung SDS) @jbeda (Joe Beda) Group #sig-scale Weekly on Thursdays at 0900 PT on Zoom (https://zoom.us/j/989573207 )
Scheduling @davidopp (David Oppenheimer, Google) @timothysc (Timothy St. Clair, Red Hat) Group #sig-scheduling Alternate between Mondays at 1 PM PT and Wednesdays at 12:30 AM PT
Storage @saad-ali (Saad Ali, Google) @childsb (Brad Childs, Red Hat) Group #sig-storage Bi-weekly Thursdays 9 AM PST (or more frequently) on Hangouts
Testing @spiffxp (Aaron Crickenberger, Samsung) @ixdy (Jeff Grafton, Google) Group #sig-testing Tuesdays at 9:30 AM PT
UI @dodwyer (David O'Dwyer, Livewyer) @preillyme (Patrick Reilly, Kismatic) @bryk (Piotr Bryk, Google) Group #sig-ui Wednesdays at 3:30 PM CEST
Windows @preillyme (Patrick Reilly, Kismatic) @sschuller (Sinclair Schuller, Apprenda Group #sig-windows Bi-weekly Tuesdays at 10:00 AM PT
Propose the new SIG publicly, including a brief mission statement, by emailing kubernetes-dev@googlegroups.com and kubernetes-users@googlegroups.com , then wait a couple of days for feedback
Create a group with at least 2 owners (and one of which should be sarahnovotny at google.com): kubernetes-sig-foo@googlegroups.com
Put a description of the topic in the welcome message
Set "Join the group" and "Post" to "Public"
Ask a repo maintainer to create a github label, if one doesn't already exist: area/foo
If you wish, request a new kubernetes.slack.com channel (#sig-foo) from @sarahnovotny. New users can join at slack.kubernetes.io .
Organize video meetings as needed. No need to wait for the Weekly Community Video Conference to discuss. Please report summary of SIG activities there.
Request a Zoom account from @sarahnovotny if you expect more than 30 attendees or attendees from China.
Add the meeting to the community meeting calendar by inviting cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com .
Use existing proposal and PR process
Announce new SIG on kubernetes-dev@googlegroups.com and ask a repo maintainer to create a kubernetes/community directory and github team for the new group
Submit a PR to add any SIG-related docs, schedules, roadmaps, etc. to your new kubernetes/community/SIG-foo directory.
Slack activity is archived at kubernetes.slackarchive.io . To start archiving a new channel invite the slackarchive bot to the channel via /invite @slackarchive