History

Kubernetes Submit Queue 9a3d2795ed Merge pull request #57143 from sttts/sttts-clientgen-no-base-dirs 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>. client-gen: remove base input dirs Were these dirs some kind of cargo cult? Removing them causes no change to the generated code. Background: having those packages in the list of input dirs makes them mandatory to exist. If people use code-gen on a project that does not vendor them (due to vendor/ pruning), code-gen fails. Fixes https://github.com/kubernetes/sample-controller/issues/8		2018-02-08 07:09:58 -08:00
..
src/k8s.io	Merge pull request #57143 from sttts/sttts-clientgen-no-base-dirs	2018-02-08 07:09:58 -08:00
BUILD	Promote v1alpha1 meta to v1beta1	2018-02-02 14:00:45 -05: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>.