You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Kubernetes Publisher dd730ded40 Merge pull request #88134 from jennybuckley/rate-limit-log-2 19 hours ago
.github delete all duplicate empty blanks 1 year ago
Godeps Merge pull request #88134 from jennybuckley/rate-limit-log-2 18 hours ago
deprecated snapshot clientsets pending context migration 3 weeks ago
discovery Refresh discovery server resources for memCacheClient in parallel 1 week ago
dynamic refactor 1 month ago
examples generated: run refactor 2 weeks ago
informers generated: run refactor 2 weeks ago
kubernetes remove authn/z.CreateContext expansions 2 weeks ago
kubernetes_test generated: run refactor 2 weeks ago
listers slim down some lister expansions 2 months ago
metadata refactor 1 month ago
pkg Autogenerated code 4 months ago
plugin/pkg/client/auth add a flag in azure auth module to omit spn: prefix in audience claim 1 month ago
rest Improve rate limiter latency logging and metrics 2 weeks ago
restmapper trivial fix typo: resouce -> resource 1 year ago
scale refactor 1 month ago
testing Allow Action's Matches function to specify a subresource. 4 weeks ago
third_party/forked/golang/template sync: initially remove files BUILD */BUILD BUILD.bazel */BUILD.bazel 1 year ago
tools Improve rate limiter latency logging and metrics 2 weeks ago
transport Plumb NextProtos to TLS client config, honor http/2 client preference 6 months ago
util add logging for csr being approved and issued. 2 weeks ago modify the error url of csi drivers 1 month ago Clarify client-go issue location (#85464) 2 months ago client-go: update to include semver tags 2 months ago
LICENSE published by bot 3 years ago
OWNERS Updated OWNERS files to include link to docs 1 year ago Update README for release 1.17 2 months ago
SECURITY_CONTACTS Update SECURITY_CONTACTS with current PSC 9 months ago Add to staging repos 2 years ago
go.mod Merge pull request #88134 from jennybuckley/rate-limit-log-2 18 hours ago
go.sum Merge pull request #88134 from jennybuckley/rate-limit-log-2 18 hours ago


Go clients for talking to a kubernetes cluster.

We recommend using the v0.x.y tags for Kubernetes releases >= v1.17.0 and kubernetes-1.x.y tags for Kubernetes releases < v1.17.0. See for detailed installation instructions. go get works, but will fetch master, which may be less stable than a tagged release.

BuildStatus Widget GoReport Widget GoDocWidget

Table of Contents

What's included

  • The kubernetes package contains the clientset to access Kubernetes API.
  • The discovery package is used to discover APIs supported by a Kubernetes API server.
  • The dynamic package contains a dynamic client that can perform generic operations on arbitrary Kubernetes API objects.
  • The plugin/pkg/client/auth packages contain optional authentication plugins for obtaining credentials from external sources.
  • The transport package is used to set up auth and start a connection.
  • The tools/cache package is useful for writing controllers.


  • For each v1.x.y Kubernetes release, the major version (first digit) would remain 0.

  • Bugfixes will result in the patch version (third digit) changing. PRs that are cherry-picked into an older Kubernetes release branch will result in an update to the corresponding branch in client-go, with a corresponding new tag changing the patch version.

Branches and tags.

We will create a new branch and tag for each increment in the minor version number. We will create only a new tag for each increment in the patch version number. See semver for definitions of major, minor, and patch.

The HEAD of the master branch in client-go will track the HEAD of the master branch in the main Kubernetes repo.

Compatibility: your code <-> client-go

The v0.x.y tags indicate that go APIs may change in incompatible ways in different versions.

See for guidelines on requiring a specific version of client-go.

Compatibility: client-go <-> Kubernetes clusters

Since Kubernetes is backwards compatible with clients, older client-go versions will work with many different Kubernetes cluster versions.

We will backport bugfixes--but not new features--into older versions of client-go.

Compatibility matrix

Kubernetes 1.15 Kubernetes 1.16 Kubernetes 1.17
kubernetes-1.15.0 +- +-
kubernetes-1.16.0 +- +-
kubernetes-1.17.0/v0.17.0 +- +-
HEAD +- +- +-


  • Exactly the same features / API objects in both client-go and the Kubernetes version.
  • + client-go has features or API objects that may not be present in the Kubernetes cluster, either due to that client-go has additional new API, or that the server has removed old API. However, everything they have in common (i.e., most APIs) will work. Please note that alpha APIs may vanish or change significantly in a single release.
  • - The Kubernetes cluster has features the client-go library can't use, either due to the server has additional new API, or that client-go has removed old API. However, everything they share in common (i.e., most APIs) will work.

See the CHANGELOG for a detailed description of changes between client-go versions.

Branch Canonical source code location Maintenance status
release-1.4 Kubernetes main repo, 1.4 branch = -
release-1.5 Kubernetes main repo, 1.5 branch = -
release-2.0 Kubernetes main repo, 1.5 branch = -
release-3.0 Kubernetes main repo, 1.6 branch = -
release-4.0 Kubernetes main repo, 1.7 branch = -
release-5.0 Kubernetes main repo, 1.8 branch = -
release-6.0 Kubernetes main repo, 1.9 branch = -
release-7.0 Kubernetes main repo, 1.10 branch = -
release-8.0 Kubernetes main repo, 1.11 branch =-
release-9.0 Kubernetes main repo, 1.12 branch =-
release-10.0 Kubernetes main repo, 1.13 branch =-
release-11.0 Kubernetes main repo, 1.14 branch
release-12.0 Kubernetes main repo, 1.15 branch
release-13.0 Kubernetes main repo, 1.16 branch
release-14.0 Kubernetes main repo, 1.17 branch
client-go HEAD Kubernetes main repo, master branch


  • Changes in main Kubernetes repo are actively published to client-go by a bot
  • = Maintenance is manual, only severe security bugs will be patched.
  • - Deprecated; please upgrade.

Deprecation policy

We will maintain branches for at least six months after their first stable tag is cut. (E.g., the clock for the release-2.0 branch started ticking when we tagged v2.0.0, not when we made the first alpha.) This policy applies to every version greater than or equal to 2.0.

Why do the 1.4 and 1.5 branch contain top-level folder named after the version?

For the initial release of client-go, we thought it would be easiest to keep separate directories for each minor version. That soon proved to be a mistake. We are keeping the top-level folders in the 1.4 and 1.5 branches so that existing users won't be broken.

Kubernetes tags

This repository is still a mirror of, the code development is still done in the staging area.

Since Kubernetes v1.8.0, when syncing the code from the staging area, we also sync the Kubernetes version tags to client-go, prefixed with kubernetes-. From Kubernetes v1.17.0, we also create matching semver v0.x.y tags for each v1.x.y Kubernetes release.

For example, if you check out the kubernetes-1.17.0 or the v0.17.0 tag in client-go, the code you get is exactly the same as if you check out the v1.17.0 tag in Kubernetes, and change directory to staging/src/

The purpose is to let users quickly find matching commits among published repos, like sample-apiserver, apiextension-apiserver, etc. The Kubernetes version tag does NOT claim any backwards compatibility guarantees for client-go. Please check the semantic versions if you care about backwards compatibility.

How to get it

Use go1.11+ and fetch the desired version using the go get command. For example:

go get

See for detailed instructions.

How to use it

If your application runs in a Pod in the cluster, please refer to the in-cluster example, otherwise please refer to the out-of-cluster example.

Dependency management

For details on how to correctly use a dependency management for installing client-go, please see

Contributing code

Please send pull requests against the client packages in the Kubernetes main repository. Changes in the staging area will be published to this repository every day.