-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[🚀 Feature]: Selenium Grid Helm Chart: Do Not Patch Keda If Disabled #2268
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
Comments
@AndreasPetersen, 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! |
Hi, for the reason the patch job is running even |
Thanks for the quick reply @VietND96 . Like you said, I specifically disabled the patcher, and upgrading the grid then works as expected. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature and motivation
We have disabled autoscaling on our Selenium Grid:
But when we update the grid, Keda is still patched, because
https://github.com/SeleniumHQ/docker-selenium/blob/trunk/charts/selenium-grid/templates/patch-keda/patch-keda-objects-job.yaml#L1
does not check if autoscaling is also enabled.
This unexpectedly caused some issues for us, as we were not expecting Keda to patch. Specifically we need to fetch our Docker images through a corporate Artifactory, so the default
kubectlImage
was being blocked, causing upgrade failure.I propose that patching of Keda is disabled if autoscaling is disabled.
Usage example
Setting
in
values.yaml
will disable Keda patching.The text was updated successfully, but these errors were encountered: