Jorge Turrado Ferrero
Jorge Turrado Ferrero
Could you fix DCO please? https://github.com/kedacore/keda/pull/5839/checks?check_run_id=36986822520 I merged the docs by mistake and this PR is left :/
/run-e2e azure **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/13258841537)
any thought @justinianvoss22 ?
I think that this is nice but I'm worried about if the waiting time is so long, as it'll look as an issue in KEDA (nothing will happen) when it's...
I was opening a PR with the same change right now, so I can confirm that this is correct since this helm commit -> https://github.com/argoproj/argo-helm/commit/1c95f37c68340326bd7fe1264d23fc1f35774a18 Could you fix the DCO...
Sorry for the slow response, we were in KubeCon xD The metric collectors are here: https://github.com/kedacore/keda/tree/main/pkg/metricscollector I think that the easiest way is starting a fresh KEDA without any CR...
Yeah, if `keda_build_info` it's the only one, keeping it clearly documented it's nice and enough :)
About CPU/Memory scaler + HTTP Add-on, this is the expected behaviour as CPU scaler can't be used for scaling from/to zero and it requires to work alongside another external metric...
I've created this issue in the upstream repo -> https://github.com/kedacore/keda/issues/6986