Jorge Turrado Ferrero

that's true, maybe the problem in Azure scalers it's different and related with not closed connections 🤔

so, in 2.4 you didn't have this problem, and now in 2.7.1 you have it, right?

I'm trying to replicate this issue but I cannot do it. Could you give me any tip to reproduce this? I'm trying dropping the cluster connection but I can't see...

I have tried the same, locking the disks by filling them (with KEDA connected all the time) and I haven't been able to reproduce your issue, once I have solved...

hey @chenele There were problems related with the internal cache in KEDA v2.5, please update it to at least v2.6.1 (or to latest v2.7.1) let me know if the problem...

The point is that AFAIR, right now that information is not passed to the scalers, so we have to pass extra information to all the scalers that is only needed...

I think that is a gap in the docs, the section `horizontalPodAutoScalerConfig` is passed to the HPA but the scaling from 1 to 0 is done by the operator. IMO,...

I'm not sure, but in this case the user problem is from 1 to 0 and the HPA doesn't work there, it's the operator itself. I mean, if the issue...

Nowadays, KEDA supports ARM64 arch, so I can tackle this issue and do the same as I did there. Do you think it's useful @arschles ?

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