[🐛 Bug]: ScaledObject errors out when ServiceName has been used - GKE

What happened?

I have setup my Cluster in GKE. Attached are my Configs fro my cluser and selenium grid.

When I use the service name in my ScaledObject trigger, it doesn't instantiate the POD. However, if I use the ClusterIP directly, then only it works.

It should work with the service name as well unless I am missing anything. It adds the request to queue using the service name. Hence I am ruling out the connectivity issues with service name. However, it doesn't create a new node/pod that was suppossed to be spinned up by ScaledObject making the node available for execution.

selenium-grid-config.txt

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

Added to description

Relevant log output

Attached in Description

Operating System

Kubernetes (GKE)

Docker Selenium version (image tag)

4.20

Selenium Grid chart version (chart version)

0.29

The issue points to the attached selenium-grid-config.txt and the ScaledObject trigger on GKE; start by reviewing that configuration and reproducing the service-name and ClusterIP cases with Selenium Grid chart 0.29. Done means identifying why the service-name case fails and confirming that the ScaledObject can instantiate the expected pod when the service name is used.