Google Git
Sign in
chromium / external / github.com / kubernetes / apimachinery / refs/heads/upstream/release-1.11
commitc182ff3b98419e7305cc361fd1811988591656cf[log] [tgz]
authorKubernetes Publisher <k8s-publishing-bot@users.noreply.github.com>Sat Feb 23 00:17:10 2019
committerKubernetes Publisher <k8s-publishing-bot@users.noreply.github.com>Sat Feb 23 00:17:10 2019
treee1f1c165be126cfb3276874cbab025bac3b08243
parent8abce45f45a12780984acd6b288b5fdf20b0ca8b [diff]
Merge pull request #74106 from caesarxuchao/automated-cherry-pick-of-#68428-#68442-#73443-#73713-#73805-#74000-upstream-release-1.11

Automated cherry pick of #68428: vendor: bump github.com/evanphx/json-patch

Kubernetes-commit: 5d86c1bcf73cdd7d77d211693b43a90456a1f26e
tree: e1f1c165be126cfb3276874cbab025bac3b08243
  1. .github/
  2. Godeps/
  3. pkg/
  4. third_party/
  5. code-of-conduct.md
  6. CONTRIBUTING.md
  7. LICENSE
  8. OWNERS
  9. README.md
  10. SECURITY_CONTACTS
README.md

apimachinery

Scheme, typing, encoding, decoding, and conversion packages for Kubernetes and Kubernetes-like API objects.

Purpose

This library is a shared dependency for servers and clients to work with Kubernetes API infrastructure without direct type dependencies. Its first consumers are k8s.io/kubernetes, k8s.io/client-go, and k8s.io/apiserver.

Compatibility

There are NO compatibility guarantees for this repository. It is in direct support of Kubernetes, so branches will track Kubernetes and be compatible with that repo. As we more cleanly separate the layers, we will review the compatibility guarantee.

Where does it come from?

apimachinery is synced from https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apimachinery. Code changes are made in that location, merged into k8s.io/kubernetes and later synced here.

Things you should NOT do

  1. Add API types to this repo. This is for the machinery, not for the types.
  2. Directly modify any files under pkg in this repo. Those are driven from k8s.io/kubernetes/staging/src/k8s.io/apimachinery.
  3. Expect compatibility. This repo is direct support of Kubernetes and the API isn't yet stable enough for API guarantees.