[🚀 Feature]: Custom Schedular or schedular name selection not supported for scaledjobs

[amarjotkalraTR]

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

[github-actions[bot]]

@amarjotkalraTR, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

Hi, can you give an example usage of schedulerName in Deployment? Since I saw this config is used in spec of kind Pod object.

[amarjotkalraTR]

Basically when keda scales the job for chrome node , I want those pods to utilize the custom scheduler . I am not sure what it means or actually required here ( changes part of kind pod).

It needs to be under deployment file or scaled jobs charts/selenium-grid/templates/chrome-node-scaledjobs.yaml