SeleniumHQ / SeleniumHQ/docker-selenium
[🚀 Feature]: Custom Schedular or schedular name selection not supported for scaledjobs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
Feature and motivation
For better utilization of underlying infrastructure , We need the feature to choose schedular name to be used.
charts/selenium-grid/templates/chrome-node-scaledjobs.yaml
Usage example
helm upgrade --install selenium-grid docker-selenium/selenium-grid --namespace selenium -- chromeNode.schedularName="customSchedular"
customSchedular is already created schedular in cluster
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 with charts/selenium-grid/templates/chrome-node-scaledjobs.yaml and inspect how the chart exposes configuration for scaled jobs. Trace the example value chromeNode.schedularName="customSchedular" through the Helm chart, then verify that an existing custom scheduler name is used by the generated scaled-job configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100