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

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

Start with the Selenium Grid 4.41 release notes and the Kubernetes deployment using selenium/hub, selenium/node-chrome, and selenium/node-firefox images. Compare that architecture with the documented Dynamic Grid and selenium/node-docker setup; done means the supported configuration and any required Kubernetes settings are clearly documented.