cannot use fuzzer.FuzzerFor(fuzzer.MergeFuzzerFuncs(funcs...)

[mcbenjemaa]

What steps did you take and what happened?

Importing CAPI v1.10.4 and running the e2e tests on our Proxmox provider causes this issue:

Failed to compile e2e:

# sigs.k8s.io/cluster-api/util/conversion
../../../../../go/pkg/mod/sigs.k8s.io/cluster-api@v1.10.4/util/conversion/conversion.go:158:9: cannot use fuzzer.FuzzerFor(fuzzer.MergeFuzzerFuncs(funcs...), rand.NewSource(rand.Int63()), runtimeserializer.NewCodecFactory(scheme)) (value of type *randfill.Filler) as *fuzz.Fuzzer value in return statement

Logs

What did you expect to happen?

e2e tests runs as usual.

Cluster API version

v1.10.4

Kubernetes version

1.31

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

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.

[sbueringer]

You have to use the same k8s.io/* dependencies as Cluster API: https://github.com/kubernetes-sigs/cluster-api/blob/v1.10.4/go.mod#L43-L49 (v0.32.x)

[mcbenjemaa]

Right, because controller-runtime was pinned.