Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to scale differently sized browser nodes on selenium-grid scaler #6080

Open
rubroboletus opened this issue Aug 15, 2024 · 1 comment · May be fixed by #6169
Open

Allow to scale differently sized browser nodes on selenium-grid scaler #6080

rubroboletus opened this issue Aug 15, 2024 · 1 comment · May be fixed by #6169
Labels
feature-request All issues for new features that have not been committed to needs-discussion

Comments

@rubroboletus
Copy link

Proposal

Currently the selenium-grid scaler needs exactly same sizing for every browser node with any browser / platform combination. We are in situation, where windows browser nodes are static and linux browser nodes are scaled by KEDA. Size of our Windows nodes is 4 browser slots / node with two browsers on each. But we wanna to scale linux nodes with just one slot and one browser per pod. In current situation it does not work well, because KEDA supposes, that all browser nodes are same size. We like to have ability to set browser node size for browser / platform combination and be able to read this size from grid, when at least one node of such combination is up.

Use-Case

No response

Is this a feature you are interested in implementing yourself?

Yes

Anything else?

No response

@rubroboletus rubroboletus added feature-request All issues for new features that have not been committed to needs-discussion labels Aug 15, 2024
@zroubalik
Copy link
Member

Sounds reasonable :)

@VietND96 VietND96 linked a pull request Sep 17, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion
Projects
Status: To Triage
Development

Successfully merging a pull request may close this issue.

2 participants