You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I attempted to use Azure Service Bus Scaler with Hashicorp Vault, accidentally in the secret path I used a path that didn't exist, also the vault roles and policies were configured for the same path which didn't exist.
Provided this circumstance, I deployed my app with scaledObject and TriggerAuth shortly after which the keda-operator crashed and went into a loop of starting up and crashing for the same reason.
Report
I attempted to use Azure Service Bus Scaler with Hashicorp Vault, accidentally in the secret path I used a path that didn't exist, also the vault roles and policies were configured for the same path which didn't exist.
Provided this circumstance, I deployed my app with scaledObject and TriggerAuth shortly after which the keda-operator crashed and went into a loop of starting up and crashing for the same reason.
I've already discussed the same in here - #1754
keda-scaler.yaml
Expected Behavior
I would expect it to not crash but handled with an appropriate error message and exception.
Actual Behavior
keda-operator crashes under the described circumstance
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.2.0
Kubernetes Version
1.19
Platform
Any
Scaler Details
Azure Service Bus Scaler
Anything else?
No response
The text was updated successfully, but these errors were encountered: