Jorge Turrado Ferrero

as [I said in the discussion](https://github.com/kedacore/keda/discussions/3306#discussioncomment-3095812), I'm not sure if we need to cover it with e2e tests TBH, adding a simple test to cover the same scenario as already...

Agree, having the issue doesn't hurt xD Maybe you achieve a huge wallet for that subscription and makes sense having that Redis 😄

I can see in the logs that is the prometheus server who refuses the connection, ``` 1.6559825743479238e+09 ERROR scalehandler Error getting scale decision {"scaledobject.Name": "transactscaledobject", "scaledObject.Namespace": "autoscale", "scaleTarget.Name": "autoscale-transactbatchservice", "error":...

Hey @MahajanSanjana29 Are you using `Deployment`? I mean, KEDA doesn't manages the autoscaling itself, KEDA delegates to the HPA Controller the job and it's the HPA Controller who decides which...

Hi, I think that using other type than string could be complicated because we should unify all the threshold names in order to have only 1 integer field. Now we...

Any opinion @kedacore/keda-core-contributors ?

> After further thought, I think I have a rough idea on how this could be done. > > The `metadata` field specifies > > https://github.com/kedacore/keda/blob/7b9817325fd88f291af6a224899bd385cb86bb3c/config/crd/bases/keda.sh_scaledobjects.yaml#L268-L269 > > which could...

I think that it's not possible right now :( Let me review your PR in depth, my concern with it is the backward compatibility and I'd like to do some...

hey, we should address it, are you willing to contribute? There are other issue related and maybe the problem in both cases comes from the same code https://github.com/kedacore/keda/issues/3151#issuecomment-1184443468

I don't want to put pressure in your back, but just for giving the whole picture. We will do a release during the first half of August and having this...