-
-
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need MinReplicaCount in ScaleObject Templates #1899
Comments
@petkovp, 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! |
I have the same situation too. I also need the possibility to define MinReplicaCount in ScaledObject. |
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. |
What happened?
When template scaleObject is turn on the pods restarted permanently.
Every 20 seconds pod restarted, because KEDA scaleDown the pod to 0.
The KEDA scaling use activation phase. More info here: https://keda.sh/docs/2.11/concepts/scaling-deployments/#activating-and-scaling-thresholds
We need from scaling phase and we need from value MinReplicaCount in ScaleObject Templates
Command used to start Selenium Grid with Docker
We need from additional value or specification in ScaleObject Templates: minReplicaCount apiVersion: keda.sh/v1alpha1 kind: ScaledObject metadata: ----------------- spec: minReplicaCount: {{ .Values.chromeNode.replicas }} maxReplicaCount: {{ .Values.chromeNode.maxReplicaCount }}
Relevant log output
Operating System
macOS
Docker Selenium version (tag)
4.10.
The text was updated successfully, but these errors were encountered: