Unexpected EOF error when trying to create a job from a cronjob in kubectl 1.32+

[bscaleb]

What happened: With kubectl client 1.32+ and server 1.33.5, running kubectl create job test --from=cronjob/any-cronjob fails with an error such as

error: failed to create job: the object provided is unrecognized (must be of type Job): unexpected EOF (6b3873000a0f0a0862617463682f763112034a6f6212efbfbd0e0aefbfbd ...)

What you expected to happen: This command should create a Job resource.

How to reproduce it (as minimally and precisely as possible): Attempt to create a Job from a CronJob via cli with the specified kube client and server versions.

Anything else we need to know?:
My AI assistant thinks it is due to protobuf serialization failure and may be related to the Go version used to build these. 1.22.x is used for 1.31.13, where this works, and 1.23.x is used for 1.32.

Environment:

• Kubernetes client and server versions (use kubectl version): Client: 1.32+ (tested on 1.32, 1.33, 1.34). Server: v1.33.5-eks-3cfe0ce
• Cloud provider or hardware configuration: AWS EKS on EC2
• OS (e.g: cat /etc/os-release): MacOS Sequoia 15.7.2 on M1 darwin/arm64

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[soltysh]

/assign

[soltysh]

What happened: With kubectl client 1.32+ and server 1.33.5, running kubectl create job test --from=cronjob/any-cronjob fails with an error such as

error: failed to create job: the object provided is unrecognized (must be of type Job): unexpected EOF (6b3873000a0f0a0862617463682f763112034a6f6212efbfbd0e0aefbfbd ...)

Can you try re-running your command with increased verbosity, like -v=9 and provide it here for further debugging?

How to reproduce it (as minimally and precisely as possible): Attempt to create a Job from a CronJob via cli with the specified kube client and server versions.

Anything else we need to know?: My AI assistant thinks it is due to protobuf serialization failure and may be related to the Go version used to build these. 1.22.x is used for 1.31.13, where this works, and 1.23.x is used for 1.32.

I've personally tried with kubectl 1.32 (latest available in release-1.32 branch) compiled with go1.25.5 and go1.23.12 against 1.33.4 and 1.35.0-rc.0 clusters. In all cases it seems to be working just fine. Protobuf does not change between golang versions, so I don't think that might be the problem here.

• Kubernetes client and server versions (use kubectl version): Client: 1.32+ (tested on 1.32, 1.33, 1.34). Server: v1.33.5-eks-3cfe0ce

• Cloud provider or hardware configuration: AWS EKS on EC2

Since your particular problem seems to be related with AWS EKS I'd consider opening an issue with them. It's possible their binary might be different that what we provide. Thus might be causing the above problems.