History

Jess Frazelle ac015892e4 add PST to main SECURITY_CONTACTS as formality Add the Product Security Team as the security contacts for the main repository and they can use the OWNERS files in each subsystem/dir to find the correct owners. Signed-off-by: Jess Frazelle <acidburn@microsoft.com>		2018-05-24 10:52:33 -04:00
..
src/k8s.io	add PST to main SECURITY_CONTACTS as formality	2018-05-24 10:52:33 -04:00
BUILD	Extract connection rotating dialer into a package	2018-05-16 10:30:53 -07:00
OWNERS	…
README.md	Add link to k8s.io/sample-controller	2017-10-19 15:46:36 +01:00

README.md

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 root:

// 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 k8s.io/<package-name>.