-
Notifications
You must be signed in to change notification settings - Fork 62
panic: runtime error: invalid memory address or nil pointer dereference #180
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
Comments
I did some digging and this looks like a problem that would be resolved by updating the dependencies to a version that supports a modern kubernetes version. I briefly tried to upgrade dependencies to test, however, there are several breaking changes due to deprecations in the package raising the errors. Since this hasn't seen a new build in 4 months, it is critical that this application is assigned to someone for ongoing maintenance considering how quickly kubernetes moves. Related: Pinned version: https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.14.5 Breaking versions:
latest version: https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.16.3 There is no compatible release in the |
Hey @lhriley! 👋🏻 Thank you for raising this with us and providing so many details. This will help us in narrowing down the problem and find out a solution to this. |
Hey @lhriley, We've got the release notes on the latest operator-sdk v1.33.0, which provide some migration steps to upgrade some dependencies and scaffolding of this project. This release came out right after we've replied to you. This migration also addresses the issue you're facing, as well as updating the project's dependencies to their latest versions. |
@edif2008 thanks for the update. Looking forward to a new release! |
@edif2008 Hey we rolled out latest version and but still fails retrieve 1P records
|
Hey @rstreics-lb, It seems that now the issue is different:
This sounds like the Connect token the operator uses is invalid. 🤔 |
Your environment
Operator Version: 1.8.0
Connect Server Version: 1.7.2
Kubernetes Version:
What happened?
Operator pod panics with the following error after recreating the pod:
What did you expect to happen?
The operator doesn't panic.
Steps to reproduce
kubectl delete -n onepassword-connect onepassword-connect-operator-abc123-xyz987
Notes & Logs
The text was updated successfully, but these errors were encountered: