Jorge Turrado Ferrero

> @JorTurFer At this moment, we only monitor CPU and Mem. I dont have any other triggers for now. Actually, we are using the combination of CPU+Mem together as trigger...

We could trigger the release in the same way that we use for the code and probably it'll make our life easier xD About supporting OCI, I'd support both, the...

I think that this is fascinating, but I'm not sure if it works correctly before the live pod resizing is in GA. I mean, restarting the operator for updating the...

Hello, I have just tried with a fresh cluster using latest helm chart (v2.11.1) and default values and I can't reproduce the issue. In my case, the apiservice points to...

recapping: You have KEDA v2.7.1 installed and you want to migrate to v2.11 but it doesn't work, right? You are using default values + the values above. Is it correct?...

> I can also provide the kubectl commands I am using to delete the Keda resources (everything except ScaledObjects) It'd be nice ❤️ I'll try to reproduce your scenario exactly

I'm going to test it soon (today or tomorrow max), but I have a question in the meantime, why didn't you just upgrade the chart using `helm upgrade`? It doesn't...

> That would be ideal. But currently we're also moving management of helm to Terraform, using the helm_release provider. AFAIK, that provider supports upgrading out-of-the-box, so you just need to...

hi @ArieLevs , It's a known bug, we removed the prometheus server by error and [we have already merged the fix](https://github.com/kedacore/keda/issues/4776), a hotfix release will be cut soon. I'd suggest...

I'd keep it as it is, why do you need this change?