The Kubernetes project leverages multiple GitHub organizations to store and organize code. This guide contains the details on how to run those organizations for CNCF compliance and for the guidelines of the community.
Kubernetes managed organizations should be in the form of kubernetes-[thing].
For example, kubernetes-client where the
API clients are housed.
Prior to creating an organization please contact the steering committee for direction and approval.
Note: The CNCF, as part of the Linux Foundation, holds the trademark on the Kubernetes name. All GitHub organizations with Kubernetes in the name should be managed by the Kubernetes project or use a different name.
Due to licensing and CLA issues, prior to transferring software into a Kubernetes managed organization there is some due diligence that needs to occur. Please contact the steering committee and CNCF prior to moving any code in.
It is easier to start new code in a Kubernetes organization than it is to transfer in existing code.
The following organizations are currently known to be part of the Kubernetes project:
- kubernetes
- kubernetes-client
- kubernetes-csi
- kubernetes-graveyard †
- kubernetes-helm
- kubernetes-incubator
- kubernetes-retired
- kubernetes-security
† kubernetes-retired should be used instead of kubernetes-graveyard going forward.
Note, this list is subject to change.
There are more organization names that we are squatting on with possible future intentions. For more details please see community issue #1407.
Repositories have additional guidelines and requirements, such as the use of CLA checking on all contributions. For more details on those please see the Kubernetes Template Project.