Jorge Turrado Ferrero

> Shall we cover this also in e2e tests? @JorTurFer ? yeah, we should

I see the advantage of this, but for achieving it we have to expose also custom metrics and not only external metrics. I'm not sure if it's worth just for...

/run-e2e internal **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/8024031213)

/run-e2e internal **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/8040280008)

don't merge this PR please, I want to review in depth why the static checks didn't detected this

/run-e2e internal **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/8303448624)

I think that we should validate it as part of admission hooks and also raise an error in the operator. Adding default value is quite weird as it's totally unrelated...

Hello, any update ?

/run-e2e cassandra **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/8114900112)

I've been thinking about this PR and I want to propose you a change to not requiring any mounted certificate to work. I've thought that we could read the values...