|author||Kubernetes Publisher <email@example.com>||Wed Apr 28 01:58:50 2021|
|committer||Kubernetes Publisher <firstname.lastname@example.org>||Tue May 18 10:23:53 2021|
Merge pull request #101053 from robscott/automated-cherry-pick-of-#100728-release-1.21 Automated cherry pick of #100728: Updating Topology Aware Hints to support "Auto" value for Kubernetes-commit: 82c76d960142c52138d2836da14c964f592301b6
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
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.
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.