[🐛 Bug]: Keda is not scaling when i set the scale type is deployment and my job is goin gin queue

What happened?

Operatoe log
unable to get external metric selenium-grid-qas/s0-selenium-grid-chrome--/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: selenium-grid-selenium-node-chrome,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: the server was unable to return a response in the time allotted, but may still be processing the request (get s0-selenium-grid-chrome--.external.metrics.k8s.io)

keda enablement in values file
keda: enabled: true metricsServer: useHostNetwork: true

Command used to start Selenium Grid with Docker (or Kubernetes)

Operatoe log 
`unable to get external metric selenium-grid-qas/s0-selenium-grid-chrome--/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: selenium-grid-selenium-node-chrome,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: the server was unable to return a response in the time allotted, but may still be processing the request (get s0-selenium-grid-chrome--.external.metrics.k8s.io)`


keda enablement in values file 
`keda:
    enabled: true
    metricsServer:
      useHostNetwork: true`

Relevant log output

`unable to get external metric selenium-grid-qas/s0-selenium-grid-chrome--/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: selenium-grid-selenium-node-chrome,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: the server was unable to return a response in the time allotted, but may still be processing the request (get s0-selenium-grid-chrome--.external.metrics.k8s.io)`

Operator log
"keda-operator.selenium-grid-qas.svc.cluster.local:9666", }. Err: connection error: desc = "transport: Error while dialing: dial tcp XXXXXXXXXXX:9666: connect: connection refused" I0417 13:32:34.062543 1 provider.go:64] "msg"="Connection to KEDA Metrics Service gRPC server has been successfully established" "logger"="keda_metrics_adapter.provider" "server"="keda-operator.selenium-grid-qas.svc.cluster.local:9666"

keda apiserver log
E0417 13:57:00.700425 1 writers.go:135] "Unhandled Error" err="apiserver was unable to write a fallback JSON response: http: Handler timeout" logger="UnhandledError" E0417 13:57:00.701566 1 timeout.go:140] "Post-timeout activity" logger="UnhandledError" timeElapsed="70.788205ms" method="GET" path="/apis/external.metrics.k8s.io/v1beta1/namespaces/selenium-grid-qas/s0-selenium-grid-chrome--" result=null

Operating System

EKS

Docker Selenium version (image tag)

latest

Selenium Grid chart version (chart version)

0.42.1

Start with the Helm values file's KEDA settings and the KEDA operator, metrics-server, and external.metrics.k8s.io log entries reported here. Reproduce on EKS using Selenium Grid chart 0.42.1, then trace the timeout and connection-refused errors. Done means the external metrics request returns successfully and the deployment scales when the queue grows.