Bug Report: Missing Package Imports in zz_generated.register.go File

[hugtale]

Description

When using register-gen from the code-generator package to automatically generate the zz_generated.register.go file, the generated file is missing the import statements for the following packages:

• k8s.io/apimachinery/pkg/runtime
• k8s.io/apimachinery/pkg/runtime/schema

This issue causes compilation errors because these packages are required for the generated GroupVersion and SchemeBuilder code to function correctly.

Steps to Reproduce

1. Use register-gen to generate a zz_generated.register.go file.
2. Attempt to compile the project.
3. Observe that the generated file is missing the necessary import statements.

Expected Behavior

The generated zz_generated.register.go file should include the following imports by default:

import (
	"k8s.io/apimachinery/pkg/runtime"
	"k8s.io/apimachinery/pkg/runtime/schema"
)

This ensures that the generated code compiles without requiring manual modification.

Environment

• code-generator version: 1.32
• Go version: 1.23.4

---

Thank you for your attention to this issue. Please let me know if further details are required.

[mrIncompetent]

PR: kubernetes/kubernetes#129307

[dprotaso]

I noticed this today - is there an earlier version to use for now?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten