-
Notifications
You must be signed in to change notification settings - Fork 49
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
GitHubSecretEngineConfig referencing vaultSecret fails with panic error #205
Comments
it looks like the path you are passing is wrong (the |
So, I enabled my KV using v2, so that's why it adds |
I ran into another situation where the Operator crashes with panic error.
I believe in such cases, the Controller should handle the error, log it, and move on. |
the first one is a bug, we should in fact check for the key |
Yeah, in the second scenario I ran into the Operator POD crashed and stayed unrecovered. Yes, the secret was not populated yet in Vault. So, I think the operator should not crash and just ignore and keep trying to check the secret in vault. |
Here is my CRD:
I see this error on vault-admin operator pod:
And here is the secret path on vault:
It seems the errors happens at this line:
vault-config-operator/api/v1alpha1/githubsecretengineconfig_types.go
Line 156 in a0f0390
The text was updated successfully, but these errors were encountered: