karmada/vendor/k8s.io/code-generator
RainbowMango 2aaaa48d2b Bump Kubernetes dependencies to v1.30.2
Bump controller-runtime to v0.18.4 and update vendor

Signed-off-by: RainbowMango <qdurenhongcai@gmail.com>
2024-07-13 16:48:07 +08:00
..
cmd Bump Kubernetes dependencies to v1.30.2 2024-07-13 16:48:07 +08:00
pkg Bump Kubernetes dependencies to v1.30.2 2024-07-13 16:48:07 +08:00
third_party/forked/golang upgrade k8s dependency to v0.22.2 2021-10-22 17:42:30 +08:00
CONTRIBUTING.md update vendor/ 2020-11-11 10:46:27 +08:00
LICENSE update vendor/ 2020-11-11 10:46:27 +08:00
OWNERS update auto-generated files 2023-12-25 10:45:22 +08:00
README.md Bump Kubernetes dependencies to v1.30.2 2024-07-13 16:48:07 +08:00
SECURITY_CONTACTS update vendor/ 2020-11-11 10:46:27 +08:00
code-of-conduct.md update vendor/ 2020-11-11 10:46:27 +08:00
doc.go Update vendor and tidy go module 2022-02-19 09:34:44 +08:00
generate-groups.sh Bump Kubernetes dependencies to v1.30.2 2024-07-13 16:48:07 +08:00
generate-internal-groups.sh Bump Kubernetes dependencies to v1.30.2 2024-07-13 16:48:07 +08:00
kube_codegen.sh Bump Kubernetes dependencies to v1.30.2 2024-07-13 16:48:07 +08:00
tools.go Bump Kubernetes dependencies to v1.30.2 2024-07-13 16:48:07 +08:00

README.md

code-generator

Golang code-generators used to implement Kubernetes-style API types.

Purpose

These code-generators can be used

  • in the context of CustomResourceDefinition to build native, versioned clients, informers and other helpers
  • in the context of User-provider API Servers to build conversions between internal and versioned types, defaulters, protobuf codecs, internal and versioned clients and informers.

Resources

Usage

The examples above are dated. The current recommended script to use is kube_codegen.sh.

Compatibility

HEAD of this repo will match HEAD of k8s.io/apiserver, k8s.io/apimachinery, and k8s.io/client-go.

Where does it come from?

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