-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
TriggerAuthentication & Vault Integration - panic when missing credentials #4964
Comments
Hi, |
Thanks for reporting, should be fixed for sure. |
Yes, would be willing to create a PR to fix this |
@BojanZelic awesome, do you think you can also include some unit test with your PR? Hashicorp stuff is missing unit tests and that's something we should improve to prevent problems like this in the future. Thanks! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Hi @BojanZelic , are you still working on this ? I could help with making the PR.
Totally agree that there is unit test missing for hashicorp stuff. I'm thinking of creating a separate issue to track the unit test so that I can work on it separately. What do you think ? @zroubalik |
Thanks! feel free to take it, haven't had a chance to work in this particular issue |
Report
When creating a TriggerAuthentication & using vault authentication, forgetting to set credentials causes the keda operator to panic
Expected Behavior
Expected it to error out or ideally just default to the the standard value that's present on almost all kubernetes pods by default
/var/run/secrets/kubernetes.io/serviceaccount/token
Actual Behavior
Keda operator panic's & starts CrashLoopBackOff()'ing
Steps to Reproduce the Problem
deploy a scaled object & a triggerauthentication without any credentials defined;
ex:
Logs from KEDA operator
KEDA Version
2.11.2
Kubernetes Version
1.26
Platform
Amazon Web Services
Scaler Details
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: