History

Kubernetes Submit Queue 2abc4742d9 Merge pull request #55456 from hzxuzhonghu/token Automatic merge from submit-queue (batch tested with PRs 55682, 55444, 55456, 55717, 55131). 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>. verify token auth file What this PR does / why we need it: verify token auth file and to prevent empty token. https://kubernetes.io/docs/admin/kubelet-tls-bootstrapping/#token-authentication-file https://kubernetes.io/docs/admin/authentication/#static-token-file Which issue(s) this PR fixes (optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged): Fixes #55434 Special notes for your reviewer: Release note: ```release-note NONE ```		2017-11-15 23:06:14 -08:00
..
src/k8s.io	Merge pull request #55456 from hzxuzhonghu/token	2017-11-15 23:06:14 -08:00
BUILD	Merge pull request #54463 from saad-ali/volumeAttachmentAPI	2017-11-14 22:05:27 -08: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>.