kubernetes

Files

Kubernetes Submit Queue aace5a7b87 Merge pull request #40449 from deads2k/client-15-types

Automatic merge from submit-queue (batch tested with PRs 40239, 40397, 40449, 40448, 40360)

move the discovery and dynamic clients

Moved the dynamic client, discovery client, testing/core, and testing/cache to `client-go`.  Dependencies on api groups we don't have generated clients for have dropped out, so federation, kubeadm, and imagepolicy.

@caesarxuchao @sttts 

approved based on https://github.com/kubernetes/kubernetes/issues/40363

2017-01-26 14:23:42 -08:00

src/k8s.io

Merge pull request #40449 from deads2k/client-15-types

2017-01-26 14:23:42 -08:00

copy.sh

move testing/core to client-go

2017-01-26 13:54:40 -05:00

godeps-json-updater.go

move pkg/client/transport to client-go

2017-01-18 07:56:01 -05:00

prime-apimachinery.sh

k8s.io/apimachinery scripts

2017-01-11 08:15:34 -05:00

README.md

make modifications for README

2016-12-02 09:54:16 +08:00

README.md

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.