kubernetes

Files

Kubernetes Submit Queue 6db099fcee Merge pull request #42275 from deads2k/cli-05-restmapper

Automatic merge from submit-queue (batch tested with PRs 41306, 42187, 41666, 42275, 42266)

discovery restmapping should always prefer /v1

The core kube API, empty group, version==v1 should always be the most preferred group and resource from a rest mapper.  This special cases that.  All the others should be based on discovery order as we previously agreed.

@kubernetes/sig-cli-pr-reviews @kubernetes/sig-api-machinery-pr-reviews 
@enj

2017-03-03 10:54:43 -08:00

src/k8s.io

Merge pull request #42275 from deads2k/cli-05-restmapper

2017-03-03 10:54:43 -08:00

copy.sh

copy.sh rewrites rev of apimachinery with dummy rev in Godeps.json; remove _vendor

2017-03-01 14:13:10 -08:00

godeps-json-updater.go

copy.sh rewrites rev of apimachinery with dummy rev in Godeps.json; remove _vendor

2017-03-01 14:13:10 -08: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.