-
Notifications
You must be signed in to change notification settings - Fork 406
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
Controller-gen panic when using go 1.22 #880
Comments
What happens if you use a recent version of controller-gen? |
FWIW, https://github.com/elastic/crd-ref-docs/blob/v0.0.10 panics as well and is using controller-tools 0.13.0 already. Not the latest, I know, but at least somewhat more recent than v0.9.0. |
Looks like the very latest does work - Now I need to see if Operator-SDK support support using that version. |
jFYI: I Will likely open an upstream issue, didn't check check if a similar issue has been created. |
We updated controller-tools to v0.14.0 in nifikop (linked above) and that avoided the panic. We'd tried v0.9.0 and v0.13.0 and they both crashed when generating CRDs. |
Operator-SDK uses Kubebuilder Kubebuilder does not support 1.22 yet Also, see that this project needs to be upgraded |
Why? This is the minimal required Go version to compile controller-tools. That doesn't mean it can't be used with 1.21 or 1.22 |
This is currently failing on a similar issue to kubernetes-sigs/controller-tools#880
This fixes panic on go1.22, see kubernetes-sigs/controller-tools#880 and golang/go#65637 Since `go get sigs.k8s.io/controller-tools` updates transitive Kubernetes dependencies this change removes it from dependencies in favor of fixed version in the Makefile. Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
This is currently failing on a similar issue to kubernetes-sigs/controller-tools#880
controller-gen 0.13.0 panics on go1.22 - updating to 0.14.0 resolves it This is a known issue #kubernetes-sigs/controller-tools/issues/880 Signed-off-by: Etai Lev Ran <elevran@gmail.com>
* update toolchain to use 1.22 * update GH actions to use go1.22 * specify go1.22 in docs * update controller-gen to 0.14 (controller-gen 0.13.0 panics on go1.22 - known issue #kubernetes-sigs/controller-tools/issues/880) --------- Signed-off-by: Etai Lev Ran <elevran@gmail.com>
This updates golang.org/x/tools to a later version which fixes the crash in kubernetes-sigs/controller-tools#880, which I believe is what is happening on the current main branch in this repository.
Also, update controller-gen from v0.13.0 to v0.14.0 to avoid kubernetes-sigs/controller-tools#880.
This avoids a nil pointer derefence when building with Go 1.22: kubernetes-sigs/controller-tools#880.
This avoids a nil pointer derefence when building with Go 1.22: kubernetes-sigs/controller-tools#880.
This avoids a nil pointer derefence when building with Go 1.22: kubernetes-sigs/controller-tools#880.
This avoids a segfault linked to Go 1.22. See kubernetes-sigs/controller-tools#880.
This avoids a segfault linked to Go 1.22. See kubernetes-sigs/controller-tools#880.
for now we can't move to 1.22 due to a controler-gen panic issue, see: kubernetes-sigs/controller-tools#880
* move api to multigroup support * move controller to multigroup support * update to golang 1.21 for now we can't move to 1.22 due to a controler-gen panic issue, see: kubernetes-sigs/controller-tools#880
Previously we were using go 1.21 without issue. After upgrading to go 1.22 using controller-gen v0.9 it results in the following
The text was updated successfully, but these errors were encountered: