SeleniumHQ/docker-selenium

[馃殌 Feature]: Allow multiple Hub pods for high availability

Open

#1,849 opened on May 15, 2023

View on GitHub
聽(13 comments)聽(0 reactions)聽(0 assignees)Shell聽(6,945 stars)聽(2,435 forks)batch import
help wanted

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

Tech stack
dockerkubernetes
Domain
devopsinfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Kubernetes basicsHelm chart knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Review the existing Helm chart configuration in the repository, particularly the values.yaml and templates/deployment.yaml files. Look for comments in this issue (#1849) discussing how to implement multiple replicas and any maintainer feedback. Consider the need for leader election or session persistence when running multiple Hub pods. Test with a simple replica count change in your Kubernetes cluster.
[馃殌 Feature]: Allow multiple Hub pods for high availability 路 SeleniumHQ/docker-selenium#1849 | Good First Issue