SeleniumHQ / SeleniumHQ/docker-selenium
[🚀 Feature]: Allow multiple Hub pods for high availability
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
Feature and motivation
Currently when running Selenium Grid in Kubernetes via the Helm-chart, the hub becomes unreachable when deploying changes. This is due to there only being one replica.
Given multiple replicas, a rollout will keep the hub reachable during a deploy.
Usage example
Having multiple replicas will make the Grid more robust.
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 locating the Helm chart's Hub deployment and its replica configuration. Check how Kubernetes service routing behaves during a rollout with multiple Hub pods, then verify that the chart supports multiple replicas while keeping the Grid reachable during changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100