-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
admission.Decoder.Decode is panicking after version bump #2695
Comments
/kind support |
https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.15.0 shows that
Not sure if you are running into issues with this or something involved with the |
@mahmud2011 Please provide more of the stacktrace (at least from: |
I ran into the same issue, and I believe the relevant change is actually #2134 |
Providing a full stack trace in case it is still needed, but my analysis above should be correct hopefully:
|
Thx, agree. This is the most likely cause |
/assign |
/kind bug |
A few issues were introduced by #5843 because of changes in the sigs.k8s.io/controller-runtime interface. The biggest issue was that the call to ctrl.NewManager was not using the Options object populated earlier in the setupManagerAndCertController function. Instead it was creating and using a new, incomplete Options object. Additionally, the decoder is no longer injected automatically, it needs to be instantiated by us. Otherwise the admission webhook panics. See kubernetes-sigs/controller-runtime#2695 Fixes #6149 Signed-off-by: Antonin Bas <[email protected]>
I updated
controller-runtime
fromv0.14.4
tov0.15.3
along withk8s.io/*
fromv0.26.2
tov0.27.7
.runtime error: invalid memory address or nil pointer dereference /usr/local/go/src/runtime/panic.go:920 +0x270 sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Decoder).DecodeRaw(0x0, {{0xc000018b00, 0x2049, 0x2529}, {0x0, 0x0}}, {0x1a42b72, 0xc000229690})
I don't see any breaking changes for this in release log. I also inspected the dump using spew couldn't figure out why it's panicking.
The text was updated successfully, but these errors were encountered: