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, and thockin.
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.
- Create a group with at least 2 owners: [email protected]
- Put a description of the topic in the welcome message
- Ask a repo maintainer to create a github label, if one doesn't already exist: area/foo
- If you wish, create a new kubernetes.slack.com channel (#sig-foo). Users can join at slack.kubernetes.io.
- Organize video meetings as needed. No need to wait for the Weekly Community Video Conference to discuss. Can 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 [email protected].
- Use existing proposal and PR process
- Announce new SIG on [email protected] and ask a repo maintainer to add it to this wiki
- Submit a PR to add any SIG-related docs, schedules, roadmaps, etc. to docs/devel/sigs/
- Slack activity is archived at kubernetes.slackarchive.io. To start archiving a new channel invite the slackarchive bot to the channel via
/invite @slackarchive