github/client-go
1
0
Fork 0
mirror of https://github.com/kubernetes/client-go.git synced 2025-10-21 22:09:33 +00:00
Code Issues Projects Releases Wiki Activity

published by bot

Browse Source 
copied from https://github.com/kubernetes/kubernetes.git
last commit is f6eb28765f85dcd9e0b3b6c094605e7fff779e42
This commit is contained in:
Kubernetes Publisher
2016-09-01 12:54:21 +00:00
parent eb638c622f
commit 3ccba384d5
21 changed files with 292 additions and 708 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -18,7 +18,17 @@ client-go has the same release cycle as the Kubernetes main repository. For exam
### How to get it
You can `go get` a release of client-go, e.g., `go get k8s.io/client-go/1.4/...` for the whole thing or `go get k8s.io/client-go/1.4/kubernetes` if you just need the clientset.
You can `go get` to get a release of client-go, e.g., `go get k8s.io/client-go/1.4/...` or `go get k8s.io/client-go/1.4/kubernetes`.
### How to use it
If your application runs in a Pod in the cluster, please refer to the in-cluster [example](examples/in-cluster/main.go), otherwise please refer to the out-of-cluster [example](examples/out-of-cluster/main.go).
### Dependency management
If your application depends on a package that client-go depends on, and you let the Go compiler find the dependency in `GOPATH`, you will end up with duplicated dependencies: one copy from the `GOPATH`, and one from the vendor folder of client-go. This will cause unexpected runtime error like flag redefinition, since the go compiler ends up importing both packages separately, even if they are exactly the same thing. If this happens, you can either
* run `godep restore` ([godep](https://github.com/tools/godep)) in the client-go/1.4 folder, then remove the vendor folder of client-go. Then the packages in your GOPATH will be the only copy
* or run `godep save` in your application folder to flatten all dependencies.
### Reporting bugs