Selenium Grid Scaler browser node pending

[jannek76]

I have tried to configure Selenium Grid Scaler to work inside of minikube and AWS kubernetes cluster.
I don't know what is going wrong, but my browser is always in pending state.

Trying to set cluster with these steps which are defined for azure, but I think these should work also in minikube or AWS.
https://github.com/Azure-Samples/selenium-grid-aks-keda#keda

Scaled objects trigger will raise correct amount of browser pods, but they will be always in pending state.

NAME                                              READY   STATUS    RESTARTS   AGE
keda-operator-5584f56d8c-kfcrv                    1/1     Running   0          17m
keda-operator-metrics-apiserver-f5d7b56d8-crwpg   1/1     Running   0          17m
selenium-chrome-node-8445756849-g5lvs             0/1     Pending   0          13m
selenium-chrome-node-8445756849-ncfjq             0/1     Pending   0          10m
selenium-hub-5ccdf74dfb-k2zgs                     1/1     Running   0          16m

minikube version: v1.23.2
latest keda and selenium-grid

and same case if starting grid
helm upgrade --install selenium-grid docker-selenium/charts/selenium-grid/. --set hub.serviceType=LoadBalancer,chromeNode.replicas=$chromeReplicas,firefoxNode.replicas=$firefoxReplicas,edgeNode.replicas=$edgeReplicas,chromeNode.nodeSelector.selbrowser=chromepool,firefoxNode.nodeSelector.selbrowser=firefoxpool,edgeNode.nodeSelector.selbrowser=edgepool,ingress.enabled=false

I am trying to run robot framework tests

python requirements

robotframework ==5.0.1
robotframework-pabot ==2.6.0
robotframework-requests ==0.9.3
robotframework-seleniumlibrary ==6.0.0
selenium ==4.4.0

testsuites/simple.robot

*** Settings ***
Library                     SeleniumLibrary

*** Variables ***
${remote_url}  http://localhost:4444
${browser}  headlesschrome


*** Keywords ***
Open Test Page
  Open Browser  https://google.fi
  ...  browser=${browser}
  ...  remote_url=${remote_url}
  Maximize Browser Window

*** Test Cases ***
Run Test
  Open Test Page
  Sleep  2s
  [Teardown]  Close Browser

Run Test 2
  Open Test Page
  Sleep  5s
  [Teardown]  Close Browser

pabot --verbose --pabotlib --processes 2 --testlevelsplit -d reports/ testsuites/simple.robot

[jannek76]

This can be closed.
Problem was that there wasn't enough cpus available