[🐛 Bug]: KEDA autoscaling is not woking as expected

[venkat-enable]

What happened?

We upgraded to version 0.38.3 and updated the autoscaling parameters at the Chrome node level as follows:

autoscaling:
scaledOptions:
minReplicaCount: 0
maxReplicaCount: 10
pollingInterval: 20

chromeNode:
scaledOptions:
minReplicaCount: 1
maxReplicaCount: 10
pollingInterval: 10

Issue:

KEDA is trying to create more than the maximum number of replicas. Could you please help explain why it is behaving this way?

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

I used this command to upgrade selenium grid

helm install my-selenium-grid selenium-grid/selenium-grid --version 0.38.3 --values values.yaml

Relevant log output

no output

Operating System

Kubernetes(GKE)

Docker Selenium version (image tag)

selenium/hub:4.27.0-20250101

Selenium Grid chart version (chart version)

0.38.3

[github-actions]

@venkat-enable, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

Hi, if using 0.38.4, would it behave the same incorrect?

[venkat-enable]

Upgraded 0.38.4 then issue got fixed. Thank you :)

[VietND96]

Yes, you might see on Grid UI with Nodes, Sessions has the logo of Windows OS. That issue we are still discussing here #2542
For the right logo, platformName, you can read this PR kedacore/keda#6437. And update Node hpa config as well as set capability from client code, to have exactly match between request, Node stereotype, and KEDA scaler metadata.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.