Malay Kumar Parida 6958535ea4 build: resolve kube code-generator version from the repo's k8s version ...

kubernetes/code-generator is versioned alongside the core k8s.io modules, so codegen should logically stay in sync with the Kubernetes version in go.mod.
So we now resolve KUBE_CODEGEN_TAG from k8s.io/apimachinery with go list instead of maintaining a separate
pin that can silently fall behind dependency bumps. This removes manual version upkeep entirely. Bumping k8s modules in
go.mod automatically picks the matching code-generator release on the next make codegen.

Also rename CODE_GENERATOR_VERSION to KUBE_CODEGEN_TAG to align with the kube_codegen.sh tooling and the CODE_GENERATOR path used by codegen.sh.
Add the generated files for latest codegen run as well.

Signed-off-by: Malay Kumar Parida <mparida@redhat.com>

2026-07-15 00:59:15 +05:30

..

clientset/versioned

build: resolve kube code-generator version from the repo's k8s version

2026-07-15 00:59:15 +05:30

informers/externalversions

build: resolve kube code-generator version from the repo's k8s version

2026-07-15 00:59:15 +05:30

listers/ceph.rook.io/v1

rgw: controller for account management

2026-03-13 11:21:46 +05:30