5be43d7e35
- Remove ownership of the upgrade / downgrade testing of k8s. Now owned by SIG Cloud Provider / GCP as it only supports GCP clusters. See: https://github.com/kubernetes/kubernetes/tree/master/test/e2e/cloud/gcp - Remove the "lock-step" coordination with SIG-Release. Historically the release waited for kubeadm to update its default k8s versions constants after a "stable-1.x" label was created. No longer needed, as kubeadm defaults to "stable-1": https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/apis/kubeadm/v1beta2/defaults.go#L36 - Add note about release "informing/blocking" test jobs. - Add sig-scheduling mention under "Out of scope". - Add sig-apps mention under "Out of scope". |
||
|---|---|---|
| .github | ||
| archive | ||
| committee-code-of-conduct | ||
| committee-product-security | ||
| committee-steering | ||
| communication | ||
| contributors | ||
| events | ||
| generator | ||
| github-management | ||
| hack | ||
| icons | ||
| mentoring | ||
| sig-api-machinery | ||
| sig-apps | ||
| sig-architecture | ||
| sig-auth | ||
| sig-autoscaling | ||
| sig-cli | ||
| sig-cloud-provider | ||
| sig-cluster-lifecycle | ||
| sig-contributor-experience | ||
| sig-docs | ||
| sig-instrumentation | ||
| sig-multicluster | ||
| sig-network | ||
| sig-node | ||
| sig-release | ||
| sig-scalability | ||
| sig-scheduling | ||
| sig-service-catalog | ||
| sig-storage | ||
| sig-testing | ||
| sig-ui | ||
| sig-usability | ||
| sig-windows | ||
| ug-big-data | ||
| ug-vmware-users | ||
| wg-api-expression | ||
| wg-component-standard | ||
| wg-data-protection | ||
| wg-iot-edge | ||
| wg-k8s-infra | ||
| wg-lts | ||
| wg-machine-learning | ||
| wg-multitenancy | ||
| wg-policy | ||
| wg-security-audit | ||
| .generated_files | ||
| .gitignore | ||
| CLA.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| OWNERS_ALIASES | ||
| README.md | ||
| SECURITY_CONTACTS | ||
| SIG-diagram.png | ||
| SIG-diagram.svg | ||
| code-of-conduct.md | ||
| community-membership.md | ||
| go.mod | ||
| go.sum | ||
| governance.md | ||
| incubator.md | ||
| kubernetes_governance_diagram.png | ||
| sig-list.md | ||
| sig-wg-lifecycle.md | ||
| sigs.yaml | ||
| values.md | ||
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-sigsgithub org.
- 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
- 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:
- How to file an issue
- How to find something to work on
- 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.