Selenium Grid Scaler is a built-in scaler is maintained in upstream KEDA repository. The scaler implementation could be found here. The official docs of the scaler could be seen here.
Now, SeleniumHQ/docker-selenium involves as the maintainer for the scaler.
In order to deliver and get feedback continuously on any new bug fixes, improvement, or features for the Selenium Grid scaler. We select the latest stable version of KEDA core, patch the scaler implementation then build and deploy KEDA container images following our image tag convention.
The stable implementation will be merged to the upstream KEDA repository frequently and will be available in the next KEDA core release.
Replace the image registry and tag of these KEDA components with the patched image tag:
docker pull selenium/keda:2.15.1-selenium-grid-20241010
docker pull selenium/keda-metrics-apiserver:2.15.1-selenium-grid-20241010
docker pull selenium/keda-admission-webhooks:2.15.1-selenium-grid-20241010
Besides that, you also can use image tag latest
or nightly
.
If you are deploying KEDA core using their official Helm chart, you can overwrite the image registry and tag by providing the following values in the values.yaml
file. For example:
image:
keda:
registry: selenium
repository: keda
tag: "2.15.1-selenium-grid-20241010"
metricsApiServer:
registry: selenium
repository: keda-metrics-apiserver
tag: "2.15.1-selenium-grid-20241010"
webhooks:
registry: selenium
repository: keda-admission-webhooks
tag: "2.15.1-selenium-grid-20241010"
If you are deployment Selenium Grid chart with autoscaling.enabled
is true
(implies installing KEDA sub-chart), KEDA images registry and tag already set in the values.yaml
. Refer to list configuration.
If you want to disable default patched KEDA image tags in Selenium Grid chart, you can set via Helm CLI --set keda.image=null
or the same in values file.
Here is list of pull requests that are under testing and will be merged to the upstream KEDA repository. You can involve to review and discuss the pull requests to help us early detect and fix any issues.
You can inspect the implementation of current Selenium Grid scaler: