Jorge Turrado Ferrero

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

> This may be too limited in scope, as DaemonSet objects are impacted and will need consideration. AFAIK, [daemonsets already publish status](https://github.com/open-telemetry/opentelemetry-operator/pull/3931) since 0.125.0 but I'm willing to extend this...

Which is the goal of this scaler? I mean, handling the traffic as a proxy and counting the opened web sockets? Connecting to a server via web socket to pull...

> I'm picking up this topic again after some time testing and gathering feedback, and right now I'm working on the e2e tests for the new functionality. > > My...

I think that we could collaborate with the SIG-Autoscaling adding the support also the the VPA Controller. AFAIK, they don't support external metrics yet, but we could add the support...

Currently, there isn't any proposal, but you can tackle it if you want and draft one. I'd say that it's still interesting for KEDA :)

> Hi, new to Keda. I would like to get some background on this and help since this work item is still open. Currently, KEDA exposes `external.metrics.k8s.io` and manages the...

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

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

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