History

Kubernetes Submit Queue d04d7b4db2 Merge pull request #67011 from charrywanganthony/default_admissionPlugins_doc Automatic merge from submit-queue (batch tested with PRs 65297, 67179, 67116, 67011, 66842). 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>. list the default enabled admission plugins Which issue(s) this PR fixes : Fixes #66979 Release note: ```release-note NONE ```		2018-08-09 08:39:38 -07:00
..
src	Merge pull request #67011 from charrywanganthony/default_admissionPlugins_doc	2018-08-09 08:39:38 -07:00
BUILD	Run hack/update-bazel.sh	2018-06-22 16:22:57 -07:00
OWNERS	…
README.md	…

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>.