You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Selenium grid helm chart helps us to deploy selenium grid into our K8S cluster, but by default data is not persistent, so for any reason pod that running hub rebooted or deleted, all existing sessions in queue will be lost, also session-node map will be lost.
so from existing helm chart i can't deploy high available selenium hub with 2 pods, also i can't use external data store advanced feature out of the box.
So i suggest to support external data store in helm, by only add db settings in values.yml.
@husseinmimiHarri, 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.
Feature and motivation
Selenium grid helm chart helps us to deploy selenium grid into our K8S cluster, but by default data is not persistent, so for any reason pod that running hub rebooted or deleted, all existing sessions in queue will be lost, also session-node map will be lost.
so from existing helm chart i can't deploy high available selenium hub with 2 pods, also i can't use external data store advanced feature out of the box.
So i suggest to support external data store in helm, by only add db settings in values.yml.
Usage example
The text was updated successfully, but these errors were encountered: