-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[馃悰 Bug]: ScaledObject errors out when ServiceName has been used - GKE #2231
Comments
@gitissuepost, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
How about if you try this config for the triggers as below? triggers:
- type: selenium-grid
metadata:
browserName: chrome
sessionBrowserName: chrome
unsafeSsl: 'true'
url: 'http://selenium-hub-ci:4444/graphql' |
@VietND96 - No luck.. It doesn't respond. I see the request in Queue to be assigned to a node. But my browser deployment doesn't splin up a pod. The script fails after 3 minute with a SessionNotCreatedException. Moreover, I observed that using IP, creates a POD for me and keep it idle when the minReplica in ScaledObject and Replica count in deployment are 0. If I am not missing anything, I am expecting the deployment to be created/modified with out any pod available. Based on request, the pods should get splinned up dynamically |
What happened?
I have setup my Cluster in GKE. Attached are my Configs fro my cluser and selenium grid.
When I use the service name in my ScaledObject trigger, it doesn't instantiate the POD. However, if I use the ClusterIP directly, then only it works.
It should work with the service name as well unless I am missing anything. It adds the request to queue using the service name. Hence I am ruling out the connectivity issues with service name. However, it doesn't create a new node/pod that was suppossed to be spinned up by ScaledObject making the node available for execution.
selenium-grid-config.txt
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Attached in Description
Operating System
Kubernetes (GKE)
Docker Selenium version (image tag)
4.20
Selenium Grid chart version (chart version)
0.29
The text was updated successfully, but these errors were encountered: