Skip to content
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

kms-vault-operator throwing error after upgrade to k8s 1.25 #108

Open
ryadav-asapp opened this issue May 26, 2023 · 0 comments
Open

kms-vault-operator throwing error after upgrade to k8s 1.25 #108

ryadav-asapp opened this issue May 26, 2023 · 0 comments

Comments

@ryadav-asapp
Copy link

After upgrading to k8s 1.25. Kms-vault-operator is throwing error can you help me understand this error from pods.

I0526 11:59:10.810973 1 request.go:665] Waited for 1.046650228s due to client-side throttling, not priority and fairness, request: GET:https://172.20.0.1:443/apis/authentication.k8s.io/v1?timeout=32s
2023-05-26T11:59:15.460Z INFO controller-runtime.metrics metrics server is starting to listen {"addr": ":8080"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0x16ef1a4]

goroutine 1 [running]:
github.com/patoarvizu/kms-vault-operator/controllers.VaultK8sAuth.login(0xc000454c90, 0x1d42168)
/workspace/controllers/kmsvaultsecret_k8sauth.go:33 +0x304
github.com/patoarvizu/kms-vault-operator/controllers.(*KMSVaultSecretReconciler).SetupWithManager(0xc0007eee40, 0x1d52888, 0xc00000a1e0, 0x1d42168, 0xc000454a90)
/workspace/controllers/kmsvaultsecret_controller.go:204 +0x105
main.main()
/workspace/main.go:76 +0x529

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant