Jorge Turrado Ferrero

what KEDA version are you using?

Could you share your KEDA logs?

> @tomkerkhove Trying to remedy the CI error : `` func ``(*ScaledJobReconciler).stopScaleLoopWhenPaused `` is unused (unused)` I have checkd your code and I can't see where you're using the function...

I think that this is useful but I'm not sure if it's something we can do from KEDA side. We could check the pods annotations and annotate them from max...

I have been thinking about this. Let's say that we agree to implement this, we could use the operator reconciliation to check if there is any pod (from workload) without...

Yes, my idea was to define a constant max value and do something like this during the reconciliation loops: 1. List all pods 2. Get currentValue from them (if all...

> I share the concern that this might not be a job for KEDA (because so far KEDA doesn't change the target workload and I'd like to keep it this...

I think that we can add these metrics about adoption, it's true that from monitoring pov could not give a lot of information, but from adoption pov it gives. I...

Don't expose another endpoint in the operator please, we are already exposing a single endpoint with the runtime-metrics (operator-sdk does it). Recently [we have talked about unifying them](https://github.com/kedacore/keda/issues/3586) in the...

Basically, instead of starting another server, you should register the metrics in the already existing server by prometheus global registry https://book.kubebuilder.io/reference/metrics.html#publishing-additional-metrics