Kubernetes community content
Go to file
Kubernetes Prow Robot f41ba061c9
Merge pull request #3295 from davidz627/feature/reconstructionMigration
Volume Reconstruction migration design
2019-03-26 18:54:48 -07:00
.github Merge pull request #3398 from mrbobbytables/update-slack-guidelines 2019-03-15 20:58:57 -07:00
archive Archive SIG Cluster Ops 2019-03-17 22:11:35 +05:30
committee-code-of-conduct Add Code of Conduct Committee to sigs.yaml 2019-03-15 18:15:56 +05:30
committee-product-security sigs.yaml: remove Jess Frazelle from Security Committee 2019-03-25 16:35:43 +00:00
committee-steering Move repos from sig-arch to steering committee 2019-03-19 18:07:25 +05:30
communication Minor typo fix in moderators.md 2019-03-26 19:53:47 +02:00
contributors Merge pull request #3295 from davidz627/feature/reconstructionMigration 2019-03-26 18:54:48 -07:00
events clarified a bit more language 2019-03-19 09:20:49 -07:00
generator Update generator OWNERS 2019-03-20 16:08:13 -07:00
github-management Fix link to Embargo Policy 2019-03-05 01:04:35 +05:30
hack Add tools file so that tools are vendored 2019-03-20 16:03:56 -07:00
icons This commit changes the Etcd icons 2019-01-30 03:22:00 +01:00
keps Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
mentoring Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
sig-api-machinery Merge pull request #3041 from shawn-hurley/kubebuilder-meeting 2019-03-07 16:42:16 -08:00
sig-apps sig apps: use raw github links for owners 2019-02-26 09:59:49 +05:30
sig-architecture Merge pull request #3489 from timothysc/arch_conformance 2019-03-20 14:30:58 -07:00
sig-auth Add multi-tenancy subproject to sig-auth 2019-03-19 19:54:45 +05:30
sig-autoscaling Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
sig-aws Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
sig-azure sig-azure: Add CSI driver subproject OWNERS 2019-03-06 14:24:10 -05:00
sig-big-data Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
sig-cli all URL pointing to kubectl-conventions.md have been fixed 2019-02-06 16:22:26 -06:00
sig-cloud-provider add @mcrute as tech lead of the cloud provider extraction/migration subproject 2019-03-24 22:48:16 -04:00
sig-cluster-lifecycle Add Cluster Addons meeting 2019-03-22 15:07:31 +01:00
sig-contributor-experience Update affiliation for cblecker and Phillels 2019-03-22 14:59:48 -07:00
sig-docs Merge pull request #3001 from zacharysarah/new-sig-docs-charter 2019-02-25 17:48:30 -08:00
sig-gcp Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
sig-ibmcloud Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
sig-instrumentation Typo Fix: Kubernetes 2019-02-06 01:45:09 +05:30
sig-multicluster Broken Links fix for 2696 (#3171) 2019-02-05 06:44:42 -08:00
sig-network Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
sig-node Merge pull request #3163 from eduartua/issue-3064-grouping-by-sig-node 2019-01-31 15:33:09 -08:00
sig-openstack Update SIG-OpenStack Meeting Time 2019-03-13 22:06:55 +01:00
sig-pm Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
sig-release Add kubernetes-sigs/k8s-container-image-promoter repo 2019-03-04 18:57:35 -08:00
sig-scalability Introduce pod startup SLI for stateful pods. 2019-02-28 13:18:27 +01:00
sig-scheduling Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
sig-service-catalog carolynvs stepping down from sig service catalog 2019-03-20 14:08:45 -05:00
sig-storage renames sig storage contributing doc to follow repo standards 2019-03-13 10:52:55 -07:00
sig-testing Merge pull request #3483 from spiffxp/add-subproject-contacts 2019-03-20 12:39:43 -07:00
sig-ui Merge pull request #3176 from jeefy/sig-ui-updates 2019-02-01 00:44:55 -08:00
sig-vmware Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
sig-windows Update CONTRIBUTING.md 2019-03-25 13:11:03 -05:00
vendor Update vendor/ 2019-03-20 16:06:37 -07:00
wg-apply Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
wg-component-standard generator: remove google groups note from all WG READMEs 2019-02-25 16:17:40 +05:30
wg-iot-edge Add stakeholder SIGs for wg-iot-edge 2019-03-20 19:03:28 -07:00
wg-k8s-infra Rename Product Security Team to Committee 2019-03-04 11:47:21 -07:00
wg-lts Rename Product Security Team to Committee 2019-03-04 11:47:21 -07:00
wg-machine-learning Merge pull request #2308 from whs-dot-hk/patch-3 2018-06-26 11:49:52 -07:00
wg-multitenancy multitenancy: update meeting schedule 2019-02-14 23:02:15 -08:00
wg-policy Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
wg-resource-management Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
wg-security-audit Add Jay to wg-security-audit 2019-03-11 16:34:24 -04:00
.generated_files Use git.k8s.io for links 2017-12-21 18:34:08 -08:00
.gitignore Add basic gitignore 2017-11-30 11:34:52 -08:00
.travis.yml Remove duplication 2017-07-14 10:20:04 +02:00
CLA.md Update CLA support contact information. 2019-03-21 13:42:42 -04:00
CONTRIBUTING.md Point contributors towards our new resources 2018-01-19 10:15:49 -05:00
LICENSE Initial commit 2016-05-02 20:36:05 -07:00
Makefile Merge pull request #3224 from mattjmcnaughton/mattjmcnaughton/bump-go-version-used-for-dockerized-makefile-targets 2019-02-07 00:14:52 -08:00
OWNERS Add Steering Committee to sigs.yaml 2019-03-15 18:15:50 +05:30
OWNERS_ALIASES sigs.yaml: remove Jess Frazelle from Security Committee 2019-03-25 16:35:43 +00:00
README.md Add User Groups to README 2019-03-05 00:31:25 +05:30
SECURITY_CONTACTS Update embargo doc link in SECURITY_OWNERS and changes PST to PSC 2019-03-08 10:23:48 -07:00
SIG-diagram.png Add updated SIG diagram 2019-02-15 14:28:42 -08:00
code-of-conduct.md Link to CoCC from our CoC page 2018-12-05 10:57:08 -06:00
communication.md Fixing link to communication doc 2018-01-29 09:26:01 -08:00
community-membership.md Add examples for member sponsorship requirements 2019-02-15 10:43:44 +05:30
go.mod Convert to use go modules 2019-03-20 16:05:59 -07:00
go.sum Convert to use go modules 2019-03-20 16:05:59 -07:00
governance.md deduping and creating gov docs 2019-03-05 18:27:29 -08:00
incubator.md Move existing github related docs to dedicated folder 2018-06-20 19:48:04 -07:00
kubernetes_governance_diagram.png Added governance document 2018-05-21 17:36:54 -07:00
sig-creation-procedure.md Update sig-creation-procedure.md 2017-08-30 10:38:48 -07:00
sig-governance.md deduping and creating gov docs 2019-03-05 18:27:29 -08:00
sig-list.md Merge pull request #3482 from philips/remove-jess-frazelle-from-security-committee 2019-03-26 06:33:17 -07:00
sig-wg-lifecycle.md Move K8sYoutubeCollaboration.md to youtube-guidelines.md 2019-03-12 15:51:03 -07:00
sigs.yaml Merge pull request #3482 from philips/remove-jess-frazelle-from-security-committee 2019-03-26 06:33:17 -07:00
values.md Move values.md from steering to the community repo 2019-01-16 19:41:21 +05:30

README.md

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.

Communicating

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

For more specific topics, try a SIG.

Governance

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/CONTRIBUTING.md), 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/README.md lead to many relevant technical topics.

Contribute

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

Membership

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.

Analytics