We have a setup of selenium grid deployed on AWS EKS . With this recent version , we are noticing that the tests are waiting in the session queue with out getting scheduled , even though nodes are available .

Below is the node stereotype :

        {
              "stereotypes": "[
      {
        "slots": 1,
        "stereotype": {
          "browserName": "chrome",
          "browserVersion": "",
          "container:hostname": "selenium-grid-selenium-node-chrome-6cb67c584c-pln2w",
          "goog:chromeOptions": {
            "binary": "\u002fusr\u002fbin\u002fgoogle-chrome"
          },
          "platformName": "any",
          "se:containerName": "selenium-grid-selenium-node-chrome-6cb67c584c-pln2w",
          "se:downloadsEnabled": true,
          "se:noVncPort": 7900,
          "se:vncEnabled": true
        }
      }
    ]"
            }

And below is the request waiting at session queue obtained using graphql endpoint

{
  "acceptInsecureCerts": true,
  "browserName": "chrome",
  "goog:chromeOptions": {
    "args": [
      "no-sandbox",
      "start-maximized",
      "ignore-certificate-errors",
      "disable-popup-blocking",
      "disable-dev-shm-usage",
      "user-agent=\\\"Mozilla\u002f5.0 (Linux x86_64) AppleWebKit\u002f537.36 (KHTML, like Gecko) Chrome\u002f105.0.0.0 Safari\u002f537.36 TestAutomation198c600b-0ad9-4120-babf-0b5f1a3f90aa\\\"",
      "remote-allow-origins=*"
    ],
    "extensions": [
    ]
  },
  "pageLoadStrategy": "eager",
  "platformName": "linux",
  "se:downloadsEnabled": true,
  "unhandledPromptBehavior": "accept"
}"

your insights on this would be helpful