Jorge Turrado Ferrero

Hey!!! Any news about this?

Any update?

We have the same problem using [redis-operator](https://github.com/spotahome/redis-operator). Sometimes the connection is detected as Standalone and another times it's detected well. Nothing change in the redis cluster. This is the output...

This is another redis cluster deployed also with that operator where we have the same problem: Redis Replica 0: ``` # Server redis_version:5.0.14 redis_git_sha1:00000000 redis_git_dirty:0 redis_build_id:128ca9cb46c8c5e1 redis_mode:standalone os:Linux 5.4.149-73.259.amzn2.x86_64 x86_64...

I'll try to replicate the problem in one testing cluster and debug internals.

@tomhobson are you setting `ConnectTimeout`? In my case, the value was too low and that produced the wrong detection because it doesn't detect the server type

/run-e2e solace* **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/2828314626)

Thanks for the improvemnt!

> Funny, the solace test seems to run fine on my dev cluster, [pastebin](https://pastebin.mozilla.org/evbmea3Q). @JorTurFer could we have any dangling resource in the cluster? I'm on vacations and I don't...

Could you take a look please @tomkerkhove ?:pray: