History

Kubernetes Submit Queue f3942e7ded Merge pull request #58817 from karlhungus/bugfix_yaml_decoder_short_buf 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>. Add test/fix for ErrShortBuffer edgecase What this PR does / why we need it: Found a bug with YAMLToJSONDecoder where subsequent reads after `io.ErrShortBuffer` would return values from the next yaml section, rather than the rest of the section I was reading. 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 #59055 https://github.com/kubernetes/kubernetes/issues/59055 Special notes for your reviewer: Release note: ```release-note YAMLDecoder Read now tracks rest of buffer on io.ErrShortBuffer ```		2018-01-31 00:18:03 -08:00
..
src/k8s.io	Merge pull request #58817 from karlhungus/bugfix_yaml_decoder_short_buf	2018-01-31 00:18:03 -08:00
BUILD	create auto-gen files	2018-01-17 16:23:03 +08: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>.