History

Kubernetes Submit Queue d336607679 Merge pull request #59871 from wojtek-t/cache_fields_and_labels 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>. Store labels and fields with object We are already computing labels and fields before putting objects in watchcache. And my tests show this is `PodToSelectableFields` is responsible for ~10% of memory allocations. This PR is supposed to fix that - let's double check by running kubemark-big on it.		2018-02-15 07:20:51 -08:00
..
src/k8s.io	Merge pull request #59871 from wojtek-t/cache_fields_and_labels	2018-02-15 07:20:51 -08:00
BUILD	code-generator: add boilerplate header	2018-02-13 12:34:54 +05:30
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>.