Google Git
Sign in
chromium/external/github.com/kubernetes/api/4bbf759a7c4c6936955c3c285e546a64253c5134
commit
4bbf759a7c4c6936955c3c285e546a64253c5134
[log]
author
Kubernetes Publisher <[email protected]>
Tue Apr 14 01:30:36 2026
committer
Kubernetes Publisher <[email protected]>
Tue Apr 14 14:22:10 2026
tree
beceb6bbb53775c1cf46a76ce3c2b7fb6d475d33
parent
3eacadcc9fe20c8f70a9e56eaec752568e6ecffa [diff]
Merge pull request #138350 from dashpole/update_prop_33

[release-1.33] Update go.opentelemetry.io/otel to v1.41.0

Kubernetes-commit: d02a44941c4f70410f1377c8363092fe8031d86e
2 files changed
tree: beceb6bbb53775c1cf46a76ce3c2b7fb6d475d33
  1. .github/
  2. admission/
  3. admissionregistration/
  4. apidiscovery/
  5. apiserverinternal/
  6. apps/
  7. authentication/
  8. authorization/
  9. autoscaling/
  10. batch/
  11. certificates/
  12. coordination/
  13. core/
  14. discovery/
  15. events/
  16. extensions/
  17. flowcontrol/
  18. imagepolicy/
  19. networking/
  20. node/
  21. policy/
  22. rbac/
  23. resource/
  24. scheduling/
  25. storage/
  26. storagemigration/
  27. testdata/
  28. code-of-conduct.md
  29. CONTRIBUTING.md
  30. doc.go
  31. go.mod
  32. go.sum
  33. LICENSE
  34. OWNERS
  35. README.md
  36. roundtrip_test.go
  37. SECURITY_CONTACTS
README.md

api

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

Purpose

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.

Compatibility

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.