Google Git
Sign in
chromium / external / github.com / kubernetes / apimachinery / refs/heads/upstream/release-1.14
commitc5d2f014d689246b84637774317fa0288dd3129b[log] [tgz]
authorKubernetes Publisher <k8s-publishing-bot@users.noreply.github.com>Fri Oct 04 07:49:56 2019
committerKubernetes Publisher <k8s-publishing-bot@users.noreply.github.com>Fri Oct 04 07:49:56 2019
tree8f0c167ba0df0b20b4c515176947c32013acfab1
parent5eb11211370a63b57cd9838e94e5bea4f8fe0e48 [diff]
Merge pull request #83435 from liggitt/automated-cherry-pick-of-#83261-upstream-release-1.14

[1.14] Automated cherry pick of #83261: bump gopkg.in/yaml.v2 v2.2.4

Kubernetes-commit: bdc7ad2ca2d8f54b59ca076981535b769627834d
tree: 8f0c167ba0df0b20b4c515176947c32013acfab1
  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.