Jorge Turrado Ferrero

In the same way, the host with **** hiding the secret doesn't makes sense as I can't use it for anything without adding more logic on top of it

Hello @marandalucas , You don't need cert manager, but you need to update the internal cert system too. (you can use cert-manager or the self-generated certs). You have to add...

@tomkerkhove @zroubalik , should we push again the chart or just being more care in the future?

Maybe we can take this issue as a good reason for deploying somehow the charts in a more automated way, WDYT?

Probably it's better if we wait until 2-3 weeks before the major release because in other case 2 charts would have to be maintained :/

During the context of this task, who will do it have to take in consideration that the resources are pending to split. They'd have been split [here](https://github.com/kedacore/charts/pull/183) in the context...

I think that it's the moment to address this issue. I created it almost 2 years ago and we still don't plan a major KEDA release. As we have recently...

I don't think so, that issue registers the metric with 0 as value, but the metric is registered. are you checking the metrics server (not the operator) in the port...

hum weird... It's possible that after metrics server restart, the counters don't exist because they are created during the first access. Do you have more than 1 metrics server instance?...

really weird... Could you [query some metric manually](https://keda.sh/docs/2.8/operate/metrics-server/) to ensure that at least one trigger is executed? I have just seen in your picture that you are using CPU trigger,...