-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update golang version and kube-builder #2991
Comments
That is probably because of the controller-gen version used.
If the above does not sort out your problem we will need further info (all steps and versions) to reproduce your issue so that we can check and see how that can be solved. |
Thanks I copy past the I think it could be a good Idea to offer a way to scaffold again the project. |
Yes. That would be great and very desirable if we could have a solution via tooling that could update the projects. See #2068 (comment) and thought about how we could achieve that. We also have the PR (WIP): https://github.com/kubernetes-sigs/kubebuilder/pull/2895/files but I am not sure if @rumstead has been able to work on it. Please, if you would like to help out please feel free to do so and also propose any other solution that you see for us to achieve this goal. Regards this issue, I think we could address the need and I am closing this one. However, feel free to re-open if you see that would be required. |
What broke? What's expected?
Hi
I recently updated golang on my computer from
1.17
to1.19
,during the process I also updated the version of kube-builder (I just reinstalled kubebuilder) from
3.3
to3.7
.But now I cannot generate code containing DeepCopy, DeepCopyInto, and DeepCopyObject method implementations.
I suppose that it's link to this field in my struct
I'm pretty sure everything was alright before the update but I might be wrong
Reproducing this issue
No response
KubeBuilder (CLI) Version
3.3.0
PROJECT version
v3
Plugin versions
Other versions
$> go version go version go1.19.1 darwin/amd64
Extra Labels
No response
The text was updated successfully, but these errors were encountered: