Min Runners Scaling comparison delay cause additional runner to be created and terminated unnecessarily #3866
Labels
bug
Something isn't working
gha-runner-scale-set
Related to the gha-runner-scale-set mode
needs triage
Requires review from the maintainers
Checks
Controller Version
0.9.3 , 0.10.1
Deployment Method
Helm
Checks
To Reproduce
Describe the bug
when we set up minRunners, the additional runner which is in standby also gets terminated without even executing any job due to delay in scaling comparison of desired runners
Describe the expected behavior
In this case, the Runner C should remain active and Runner D should not have get created.
Additional Context
Controller Logs
Runner Pod Logs
The text was updated successfully, but these errors were encountered: