Go clients for talking to a kubernetes cluster.
kubernetespackage contains the clientset to access Kubernetes API.
discoverypackage is used to discover APIs supported by a Kubernetes API server.
dynamicpackage contains a dynamic client that can perform generic operations on arbitrary Kubernetes API objects.
transportpackage is used to set up auth and start a connection.
tools/cachepackage is useful for writing controllers.
Each top-level folder (e.g., 1.4) contains a release of clients and their dependencies.
client-go has the same release cycle as the Kubernetes main repository. For example, in the 1.4 release cycle, the contents in
1.4/ folder are subjected to changes. Once 1.4 is released, new changes will go into the
1.5/ folder. We will make great efforts to not change the public interface of a version of the client once that version has been released. We may change the interface between versions. Old versions of the client will be retained for two release cycles.
How to get it
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 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
godep restore (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.
Please report bugs to the main Kubernetes repository.
Please send pull requests against the client packages in the Kubernetes main repository, and run the
/staging/src/k8s.io/client-go/copy.sh script to update the staging area in the main repository. Changes in the staging area will be published to this repository every day.