k3s/staging
Kubernetes Submit Queue 35b38a342b Merge pull request #52078 from sttts/sttts-codegen-owners
Automatic merge from submit-queue

code-generator: add myself to OWNERS
2017-09-13 06:58:39 -07:00
..
src/k8s.io Merge pull request #52078 from sttts/sttts-codegen-owners 2017-09-13 06:58:39 -07:00
BUILD Merge pull request #50708 from DirectXMan12/versions/autoscaling-v2beta1 2017-09-06 15:46:24 -07:00
OWNERS
README.md Fixup after k8s.io/{kube-gen -> code-generator} rename 2017-08-17 17:55:12 +02:00
godeps-json-updater.go
prime-apimachinery.sh Fixup after k8s.io/{kube-gen -> code-generator} rename 2017-08-17 17:55:12 +02: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>.