Jorge Turrado Ferrero

hey @kunalchandratre1 , I'm not getting the source that you want to scale based on. Where is this metric stored? Is your application reporting this metric to any place?

atm, there are linters without support to go 1.18 ``` WARN [linters context] bodyclose is disabled because of go1.18. You can track the evolution of the go1.18 support by following...

I agree with @tomkerkhove adding a `Dapr` strategy because it has value itself and for future product integrations, we can support also the `checkpointStrategyTemplate/chekpointPrefix`

Are there any errors in aad-pod-identity pods?

we need to use [golang 1.18](https://github.com/kedacore/keda/issues/3205) before because the new pkg [requires 1.18](https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/messaging/azservicebus#prerequisites). It's in my radar to update the library once we use go 1.18

Nice! Maybe after next release we can take a look. AFAIR, there are problems related with the golint because some checks are not ported due to a limitation in some...

> Hey @JorTurFer, are there any other blockers or can this be started now that #3653 is merged? It's already done here :smile: https://github.com/kedacore/keda/pull/3639

I agree

yes, we use argo-rollouts to test KEDA with custom resources with /scale but we don't support scaling base on them

I'm not 100% sure about this, if we expose the value, anyone in the cluster could go and get the value from there 🤔 Apart from that, I'd add it...