-
-
Notifications
You must be signed in to change notification settings - Fork 862
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
SIGSEGV invalid memory address or nil pointer dereference #2344
Comments
Hi @ziouf . Can you share which eso CRDs did you create when this issue appeared? |
None, the issue appeared at operator startup This is a very new problem after upgraded k8s from 1.26.x to 1.27.1 It used to work well on 1.26.x with the same setup |
I don't know if it share the same root cause, but I'm having the same issue with ECK operator (elastic/cloud-on-k8s#6848) Other operators are working as expected |
It looks like the panic appears when the configuration is loaded. I tried to read the code but I'm not experienced enough in go. |
Does version 0.8.1 also crashes? |
exact same behaviour with 0.8.1 |
Kubernetes 1.27 isn't supported yet, controller-runtime is blocking us to compile against client-go 1.27 |
@moolen controller-runtime v0.15.x has been released some hours ago with support of k8s v1.27 (if I understood well) https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.15.0 |
That's some great news! We'll upgrade and prep a release asap. |
@moolen maybe this comment could be a quick win : metallb/metallb#1893 (comment) And there is a lot af breaking changes with [email protected] |
Describe the bug
SIGSEGV signal at pod startup
To Reproduce
Steps to reproduce the behavior:
provide all relevant manifests
external-secrets
fromhttps://charts.external-secrets.io
including CRDsprovide the Kubernetes and ESO version
Expected behavior
Operator pod starts without any error
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: