Closed madyarini closed 1 year ago
Hi I have not experience with "security groups" but I guess that it's something like, if you are in this namespace, you can call to here, if you aren't you can't. Is something like that? If it's that, you need to ensure that the namespace where KEDA is, has access too. KEDA executes all the requests from the namespace where KEDA is (even if the resources are in other namespaces).
sorry, nvm, turns out i typo enableTls. should be enableTLS
Report
I'm facing similar issue as https://github.com/kedacore/keda/issues/2903 but I'm not sure how to reopen that issue, hence creating new issue I'm unable to connect to Elasticache due to I/O timeout my Elasticache has no Redis AUTH, it's secured by security groups. im ensured that my security groups are properly configured as in the kubernetes namespace where i placed my scaledobject & triggerauthentication, the pods are able to connect to Redis.
triggerauthentication
I have also tried adding parameter password on the trigger auth with blank string, but it's the same issue. Thanks
Expected Behavior
Able to connect to elasticache
Actual Behavior
there are error events:
Warning KEDAScalerFailed 45m keda-operator connection to redis failed: read tcp 172.31.103.20:33830->10.10.138.178:6379: i/o timeout
Steps to Reproduce the Problem
keda version: 2.8.4
Logs from KEDA operator
KEDA Version
Other
Kubernetes Version
1.25
Platform
Amazon Web Services
Scaler Details
Redis List
Anything else?
No response