b705835bae
Automatic merge from submit-queue (batch tested with PRs 43694, 41262, 42911) combine kube-apiserver and kube-aggregator This combines several pulls currently in progress and wires them together. The aggregator sits in front of the normal kube-apiserver and allows local fallthrough instead of proxying. @kubernetes/sig-api-machinery-misc @DirectXMan12 since you seem invested, your life will get easier @luxas FYI since you've started trying to wire something together. Dependent Pulls LGTM: - [x] https://github.com/kubernetes/kubernetes/pull/42801 - [x] https://github.com/kubernetes/kubernetes/pull/42886 - [x] https://github.com/kubernetes/kubernetes/pull/42900 - [x] https://github.com/kubernetes/kubernetes/pull/42732 - [x] https://github.com/kubernetes/kubernetes/pull/42672 - [x] https://github.com/kubernetes/kubernetes/pull/43141 - [x] https://github.com/kubernetes/kubernetes/pull/43076 - [x] https://github.com/kubernetes/kubernetes/pull/43149 - [x] https://github.com/kubernetes/kubernetes/pull/43226 - [x] https://github.com/kubernetes/kubernetes/pull/43144
This staging/src/k8s.io/client-go directory is the staging area of the client repo. It contains a versioned client, tools built around the client like the reflector, and all the client dependencies. The content will be periodically published to k8s.io/client-go repo.
The staged content is copied from the main repo, i.e., k8s.io/kubernetes, with directory rearrangement and necessary rewritings. To sync the content with the latest code in your local k8s.io/kubernetes, you need to run godep restore in k8s root directory, then run staging/copy.sh.
vendor/k8s.io/client-go is a symlink pointing to this staging area, so to use the packages in the staging area, you can import it as "vendor/client-go/", as if the client were vendored. The client will be vendored from k8s.io/client-go for real after the test matrix is converted to vendor k8s components.