[🐛 Bug]: Selenium Grid 4.41.0 on Kubernetes does not exhibit Dynamic Grid behavior after upgrading Hub and Nodes

[rishabhjainrj01]

What happened?

Current Setup

We have recently upgraded our Selenium Grid deployment running on Kubernetes to the following images:

selenium/hub:4.41.0-20260222
selenium/node-chrome:4.41.0-20260222
selenium/node-firefox:4.41.0-20260222

Our deployment follows the traditional Selenium Grid architecture with a Hub and dedicated Chrome and Firefox Node deployments.

Expected Behavior

Based on the Selenium 4.41 release notes and the Dynamic Grid improvements, we expected the Grid to leverage Dynamic Grid capabilities, or at least exhibit behavior different from previous releases with respect to browser session provisioning.

Actual Behavior

After upgrading, the Grid continues to behave exactly like the classic Hub + Node setup:

1. Browser Nodes remain long-running.
2. Sessions are routed to the existing browser nodes.
3. No dynamic browser provisioning is observed.
4. The overall behavior appears unchanged from previous Selenium Grid versions.

Question

Is there any additional configuration required to enable the Dynamic Grid functionality in Selenium Grid 4.41?

Specifically, we'd like to understand:

1. Is simply upgrading to the latest selenium/hub, selenium/node-chrome, and selenium/node-firefox images expected to enable Dynamic Grid functionality?
2. Is Dynamic Grid only supported when using a different deployment model (for example, selenium/node-docker) rather than the traditional Hub + Node architecture?
3. If Dynamic Grid is supported on Kubernetes, is there any additional configuration or documentation that needs to be followed to enable this behavior?

If our expectation is incorrect, could you please clarify the recommended deployment architecture for running Dynamic Grid on Kubernetes?

Environment

Selenium Grid Version: 4.41.0-20260222
Deployment Platform: Kubernetes
Images:
selenium/hub:4.41.0-20260222
selenium/node-chrome:4.41.0-20260222
selenium/node-firefox:4.41.0-20260222

Additional Context

We may have misunderstood the intended usage of Dynamic Grid. We're raising this issue primarily to understand whether any additional setup is required or whether Dynamic Grid is intended to work only with a different deployment architecture. Any clarification or documentation reference would be greatly appreciated.

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

kubectl deploy test-selenium-hub -n spr-ops

Relevant log output

NA

Operating System

macOS

Docker Selenium version (image tag)

selenium/hub:4.41.0-20260222

Selenium Grid chart version (chart version)

No response

[github-actions]

@rishabhjainrj01, 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!

[rishabhjainrj01]

@VietND96
Can you please help me understand on this once

[VietND96]

Dynamic Grid is another container component, that is not Node container as normally.
Please refer to https://github.com/SeleniumHQ/docker-selenium/tree/trunk/kubernetes/DynamicGrid

[rishabhjainrj01]

Thanks for sharing this, @VietND96

From what I understand, it looks like I would need to set up the entire environment from scratch.

At the moment, I already have the following Selenium Grid setup running:

If I want to add support for Dynamic Grid, what changes would be required in this existing setup? Specifically, which components would need to be modified or replaced, and is there a migration path from the current setup without rebuilding everything from scratch?

Image tags that I am using are already added in above thread.