kubernetes

Files

Kubernetes Submit Queue 97889d4ff9 Merge pull request #45432 from deads2k/agg-30-status

Automatic merge from submit-queue (batch tested with PRs 44798, 45537, 45448, 45432)

use apiservice.status to break apart controller and handling concerns

Still needs tests.

This starts breaking the handler and controller aspects of the aggregator by making use of status and conditions instead of actually running a specific check on demand.

@kubernetes/sig-api-machinery-pr-reviews 
@luxas since you've been asking

2017-05-09 08:29:40 -07:00

src/k8s.io

Merge pull request #45432 from deads2k/agg-30-status

2017-05-09 08:29:40 -07:00

copy.sh

remove references to client-go/pkg/api

2017-05-02 17:16:06 -07:00

godeps-json-updater.go

Clean up staging/godeps-json-updater.go

2017-04-06 09:32:57 +02:00

OWNERS

Add OWNERS for staging and api

2017-04-19 15:58:09 -04: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.