History

Kubernetes Submit Queue ee13444144 Merge pull request #50603 from shiywang/loop Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Fix Content negotiation incorrect when Accept header uses type parame… Fixes https://github.com/kubernetes/kubernetes/issues/50519 @smarterclayton @liggitt still wip, I'll add some unit test soon, and simplify the logic		2017-12-11 17:57:54 -08:00
..
src/k8s.io	Merge pull request #50603 from shiywang/loop	2017-12-11 17:57:54 -08:00
BUILD	generated	2017-11-22 18:40:09 +00: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>.