SeleniumHQ / SeleniumHQ/docker-selenium
[🐛 Bug]: Selenium-grid Autoscaling setup
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
What happened?
I have implemented Selenium-grid autoscaling on our AKS cluster using deployment files. Currently we have selenium-hub, selenium-node-chrome. Autoscaling is not enabled yet. We have two pods of selenium-node-chrome and We try to run three threads against these node-chrome pods, two get executed and one stays in the queue and fails after sometime. Its fair as autoscaling is not enabled and No. of concurrent sessions is set to "1". I am having a hard time understanding on how to setup this Autoscaling using the KEDA. Is there any clear documentation to how the autoscaling can be setup.
Command used to start Selenium Grid with Docker (or Kubernetes)
N/A
Relevant log output
N/A
Operating System
Linux
Docker Selenium version (image tag)
4.18.0
Selenium Grid chart version (chart version)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the deployment files for selenium-hub and selenium-node-chrome, then examine how KEDA can observe the Grid workload on AKS. Done means adding clear documentation for enabling autoscaling, including the two-pod, three-thread scenario and the concurrent-session setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100