Jorge Turrado Ferrero

It makes sense to me. Currently there are tools like OpenLens which already join the items with ',', but it's true that we could store the string already prepared in...

Thanks for the PR 😄 This behaviour is documented here: https://github.com/kedacore/http-add-on/blob/main/docs/walkthrough.md#routing-to-the-right-service  Personally I'd prefer to wait until going to GA, but maybe @zroubalik and @tomkerkhove have other opinion

I see the benefit of unifying them, but I'm afraid about the impact. Currently, that service is the touchpoint that users use for their ingresses and changing it will break...

> I see the point, but I think the sooner we do the change the lesser impact Yes, totally. My point is that ScalingSet feature can offer an smooth migration...

> Yes, so that's another incetive for you to complete ScalingSets ASAP :)) lol, no pressure xD > So let's try to merge this once ScalingSets are completed My point...

Yeah, agreed with @wozniakjan

Thanks for reporting! We are going to upgrade golang version asap

> [@JorTurFer](https://github.com/JorTurFer) : gcr.io/kubebuilder/kube-rbac-proxy:v0.13.0 is still referenced in the `values.yaml`. Why is that? > > Maybe: > > ``` > kubeRbacProxy: > name: quay.io/brancz/kube-rbac-proxy > tag: v0.20.0 > ``` >...

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

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