External Repository Staging Area
This directory is the staging area for packages that have been split to their own repository. The content here will be periodically published to respective top-level k8s.io repositories.
Repositories currently staged here:
The code in the staging/ directory is authoritative, i.e. the only copy of the code. You can directly modify such code.
Using staged repositories from Kubernetes code
Kubernetes code uses the repositories in this directory via symlinks in the
vendor/k8s.io directory into this staging area. For example, when
Kubernetes code imports a package from the
k8s.io/client-go repository, that
import is resolved to
staging/src/k8s.io/client-go relative to the project
// pkg/example/some_code.go package example import ( "k8s.io/client-go/dynamic" // resolves to staging/src/k8s.io/client-go/dynamic )
Once the change-over to external repositories is complete, these repositories
will actually be vendored from
Creating a new repository in staging
Adding the staging repository in
Send an email to the SIG Architecture mailing list and the mailing list of the SIG which would own the repo requesting approval for creating the staging repository.
Once approval has been granted, create the new staging repository.
Add a symlink to the staging repo in
import-restrictions.yamlto add the list of other staging repos that this new repo can import.
Add all mandatory template files to the staging repo as mentioned in https://github.com/kubernetes/kubernetes-template-project.
Make sure that the
CONTRIBUTING.mdfiles mention that PRs are not directly accepted to the repo.
Creating the published repository
Create an issue in the
kubernetes/orgrepo to request creation of the respective published repository in the Kubernetes org. The published repository must have an initial empty commit. It also needs specific access rules and branch settings. See #kubernetes/org#58 for an example.
Once the repository has been created in the Kubernetes org, update the publishing-bot to publish the staging repository by updating:
Add the staging and published repositories as a subproject for the SIG that owns the repos in
Add the repo to the list of staging repos in this