Kubernetes release v1.20.7

Based on https://github.com/kubernetes/kubernetes/releases/tag/v1.20.7
Update dependencies to v0.20.7 tag
3 files changed
tree: 5216f430e07750f2ebf4fbb58a8a97c93953a6d5
  1. .github/
  2. admission/
  3. admissionregistration/
  4. apiserverinternal/
  5. apps/
  6. authentication/
  7. authorization/
  8. autoscaling/
  9. batch/
  10. certificates/
  11. coordination/
  12. core/
  13. discovery/
  14. events/
  15. extensions/
  16. flowcontrol/
  17. Godeps/
  18. imagepolicy/
  19. networking/
  20. node/
  21. policy/
  22. rbac/
  23. scheduling/
  24. storage/
  25. testdata/
  26. code-of-conduct.md
  28. go.mod
  29. go.sum
  31. OWNERS
  32. README.md
  33. roundtrip_test.go


Schema of the external API types that are served by the Kubernetes API server.


This library is the canonical location of the Kubernetes API definition. Most likely interaction with this repository is as a dependency of client-go.

It is published separately to avoid diamond dependency problems for users who depend on more than one of k8s.io/client-go, k8s.io/apimachinery, k8s.io/apiserver...

Recommended Use

We recommend using the go types in this repo. You may serialize them directly to JSON.

If you want to store or interact with proto-formatted Kubernetes API objects, we recommend using the “official” serialization stack in k8s.io/apimachinery. Directly serializing these types to proto will not result in data that matches the wire format or is compatible with other kubernetes ecosystem tools. The reason is that the wire format includes a magic prefix and an envelope proto. Please see: https://kubernetes.io/docs/reference/using-api/api-concepts/#protobuf-encoding

For the same reason, we do not recommend embedding these proto objects within your own proto definitions. It is better to store Kubernetes objects as byte arrays, in the wire format, which is self-describing. This permits you to use either JSON or binary (proto) wire formats without code changes. It will be difficult for you to operate on both Custom Resources and built-in types otherwise.


Branches track Kubernetes branches and are compatible with that repo.

Where does it come from?

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

Things you should NOT do

  1. https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/api is synced to k8s.io/api. All changes must be made in the former. The latter is read-only.