Jorge Turrado Ferrero

Thanks for the idea! It makes sense totally 😄 Are you willing to contribute with the feature?

I think that these docs can be interesting: - How to contribute with scalers: https://github.com/kedacore/keda/blob/main/CONTRIBUTING.md#contributing-scalers - How to setup the env, run, debug, etc: https://github.com/kedacore/keda/blob/main/BUILD.md

Hello! Do you see any error in keda operator logs?

The problem is the KEDA operator pod in this case, so we need those logs. What about previous container logs?

How many ScaledObect do you have?

Are you using latest version of KEDA, right? Could you extract a memory profile and share it please? https://keda.sh/docs/2.13/troubleshooting/#troubleshoot-keda-errors-using-profiling

> Could you extract a memory profile and share it please? https://keda.sh/docs/2.13/troubleshooting/#troubleshoot-keda-errors-using-profiling

I think that it'll work with arm64 too, the post is quite old, can you give a try? pprof is a standard in golang

Could you share your TriggerAuthentication too? are you using `aws-eks` or `aws`?

Okey, if you remove the SQS ScaledObject temporally, does KEDA become stable? I mean, we are sure that's the SQS Scaler, right? We detected some problems with `aws-eks` authentication and...