Skip to content
Kubernetes community content
Branch: master
Clone or download
Latest commit 2c01ad6 Jul 19, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update slack guidelines with new moderation functionality. Apr 16, 2019
archive Archive SIG Cluster Ops Mar 17, 2019
committee-code-of-conduct Move election process into a separate document Jul 3, 2019
committee-product-security Onboard Jonathan Pulsifer to PSC Jul 9, 2019
committee-steering Switching employer for Dims Jun 17, 2019
communication Merge pull request #3905 from vllry/sig-usability-slack Jul 18, 2019
contributors Fix broken anchor links in style guide. Jul 19, 2019
events added link to SIG contributor event doc Jul 4, 2019
generator Validate same github id has same name/compay May 6, 2019
github-management github: update instructions for creating repos from template repo Jun 26, 2019
hack Add more details to Jun 26, 2019
icons This commit changes the Etcd icons Jan 30, 2019
mentoring mentoring: add nikhita as approver Jul 1, 2019
sig-api-machinery Add kubebuilder group to server-sdk subproject Jul 9, 2019
sig-apps Updating the SIG Apps contributing docs Jul 17, 2019
sig-architecture add new api review process goal Jul 9, 2019
sig-auth Fix node-identity-and-isolation subproject name May 22, 2019
sig-autoscaling Fix node-identity-and-isolation subproject name May 22, 2019
sig-aws added link to meeting recordings for sig-aws May 31, 2019
sig-azure sig-azure: Update SIG Azure Chairs Jun 6, 2019
sig-cli Merge pull request #3695 from Liujingfang1/master Jun 3, 2019
sig-cloud-provider ownership change for sig-vmware subprojects Jul 11, 2019
sig-cluster-lifecycle update SCL in China Jul 12, 2019
sig-contributor-experience Merge pull request #3622 from spzala/sigtriage Jul 10, 2019
sig-docs Fix link for issues/PRs Jun 27, 2019
sig-gcp Ran make May 3, 2019
sig-ibmcloud Ran make May 3, 2019
sig-instrumentation Add subproject slack channels May 15, 2019
sig-multicluster Rename federation-v2 to Kubefed May 15, 2019
sig-network Fixed broken sig-network meeting link May 27, 2019
sig-node Add subproject slack channels May 15, 2019
sig-openstack Ran make May 3, 2019
sig-pm sig-pm: Update SIG PM Chairs Jun 5, 2019
sig-release Add release-notes to release-engineering subproject May 12, 2019
sig-scalability Update timezone of sig-scalability public meetings Jul 19, 2019
sig-scheduling Ran make May 6, 2019
sig-service-catalog Update sig-service-catalog chairs Jul 1, 2019
sig-storage Ran make May 3, 2019
sig-testing Add some sig testing presentations Jun 22, 2019
sig-ui Update meeting time for SIG-UI Bi-Weekly Jun 13, 2019
sig-usability Removed '?' after Pivotal Jul 19, 2019
sig-vmware ownership change for sig-vmware subprojects Jul 11, 2019
sig-windows sig-windows: add windows-tools subproject Jun 2, 2019
ug-big-data revert changes to UG Big Data resource names May 7, 2019
vendor Upgrade to May 3, 2019
wg-apply Ran make May 3, 2019
wg-component-standard Add stealthybox as wg-component-standard co-chair Jun 20, 2019
wg-iot-edge Ran make May 6, 2019
wg-k8s-infra Switching employer for Dims Jun 17, 2019
wg-lts Ran make May 3, 2019
wg-machine-learning Ran make May 6, 2019
wg-multitenancy Ran make May 6, 2019
wg-policy Ran make May 6, 2019
wg-resource-management Ran make May 6, 2019
wg-security-audit Add stakeholder SIGs for wg-security-audit Jun 8, 2019
.generated_files Use for links Dec 22, 2017
.gitignore Add basic gitignore Nov 30, 2017 State CNCF abbreviation May 27, 2019 Fix links to contributor cheatsheet May 9, 2019
LICENSE Initial commit May 3, 2016
Makefile Merge pull request #3224 from mattjmcnaughton/mattjmcnaughton/bump-go… Feb 7, 2019
OWNERS Add Steering Committee to sigs.yaml Mar 15, 2019
OWNERS_ALIASES Initial draft of SIG-Usability. Jul 17, 2019 Add User Groups to README Mar 4, 2019
SECURITY_CONTACTS Update embargo doc link in SECURITY_OWNERS and changes PST to PSC Mar 8, 2019
SIG-diagram.png Add updated SIG diagram Feb 15, 2019 Link to CoCC from our CoC page Dec 5, 2018 Fixing link to communication doc Jan 29, 2018 Add examples for member sponsorship requirements Feb 15, 2019
go.mod Upgrade to May 3, 2019
go.sum Upgrade to May 3, 2019 Add User Group governance May 18, 2019 Move existing github related docs to dedicated folder Jun 21, 2018
kubernetes_governance_diagram.png Added governance document May 22, 2018 Removed '?' after Pivotal Jul 19, 2019 Fix up broken link to UG governance Jul 10, 2019
sigs.yaml Removed '?' after Pivotal Jul 19, 2019 Move from steering to the community repo Jan 16, 2019

Kubernetes Community

Welcome to the Kubernetes community!

This is the starting point for joining and contributing to the Kubernetes community - improving docs, improving code, giving talks etc.

To learn more about the project structure and organization, please refer to Project Governance information.


The communication page lists communication channels like chat, issues, mailing lists, conferences, etc.

For more specific topics, try a SIG.


Kubernetes has the following types of groups that are officially supported:

  • Committees are named sets of people that are chartered to take on sensitive topics. This group is encouraged to be as open as possible while achieving its mission but, because of the nature of the topics discussed, private communications are allowed. Examples of committees include the steering committee and things like security or code of conduct.
  • Special Interest Groups (SIGs) are persistent open groups that focus on a part of the project. SIGs must have open and transparent proceedings. Anyone is welcome to participate and contribute provided they follow the Kubernetes Code of Conduct. The purpose of a SIG is to own and develop a set of subprojects.
    • Subprojects Each SIG can have a set of subprojects. These are smaller groups that can work independently. Some subprojects will be part of the main Kubernetes deliverables while others will be more speculative and live in the kubernetes-sigs github org.
  • Working Groups are temporary groups that are formed to address issues that cross SIG boundaries. Working groups do not own any code or other long term artifacts. Working groups can report back and act through involved SIGs.
  • User Groups are groups for facilitating communication and discovery of information related to topics that have long term relevance to large groups of Kubernetes users. They do not have ownership of parts of the Kubernetes code base.

See the full governance doc for more details on these groups.

A SIG can have its own policy for contribution, described in a README or CONTRIBUTING file in the SIG folder in this repo (e.g. sig-cli/, and its own mailing list, slack channel, etc.

If you want to edit details about a SIG (e.g. its weekly meeting time or its leads), please follow these instructions that detail how our docs are auto-generated.

Learn to Build

Links in contributors/devel/ lead to many relevant technical topics.


A first step to contributing is to pick from the list of kubernetes SIGs. Start attending SIG meetings, join the slack channel and subscribe to the mailing list. SIGs will often have a set of "help wanted" issues that can help new contributors get involved.

The Contributor Guide provides detailed instruction on how to get your ideas and bug fixes seen and accepted, including:

  1. How to file an issue
  2. How to find something to work on
  3. How to open a pull request


We encourage all contributors to become members. We aim to grow an active, healthy community of contributors, reviewers, and code owners. Learn more about requirements and responsibilities of membership in our Community Membership page.


You can’t perform that action at this time.