History

Kubernetes Submit Queue cef2d325ee Merge pull request #66395 from awly/fix-kubelet-exec-plugin-startup 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>. Update http.Transport if it already exists in ExecProvider What this PR does / why we need it: This unbreaks ExecPlugin. Without the change, we hit this error https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/transport/transport.go#L32 Release note: ```release-note Fix kubelet startup failure when using ExecPlugin in kubeconfig ```		2018-07-26 10:47:05 -07:00
..
src	Merge pull request #66395 from awly/fix-kubelet-exec-plugin-startup	2018-07-26 10:47:05 -07:00
BUILD	Run hack/update-bazel.sh	2018-06-22 16:22:57 -07: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>.