-
Notifications
You must be signed in to change notification settings - Fork 826
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
FleetAutoscaler with Counter policy trying to scale Fleet to negative replicas count #3954
Comments
Just checking because the title is a bit confusing - did the Fleet go to negative replica count because you ended up with multiple FleetAutoscalers pointing at the same Fleet? Basically making sure this isn't two bugs, not just one. |
I have multiple FleetAutoscaler with there own Fleet:
When I'm testing autoscaler in any of qa*, I see that it's trying to go to negative numbers. As a quick fix for that moment is to add namespace suffix to names:
|
'This issue is marked as Stale due to inactivity for more than 30 days. To avoid being marked as 'stale' please add 'awaiting-maintainer' label or add a comment. Thank you for your contributions ' |
ooh, we should definitely fix this. |
What happened:
I had an issue with the fleet auto scaler trying to scale to -41 replicas.
As I see, fleet auto scaler with Counter policy does not respect the game server's namespace when calculating the current game server count.
I have different namespaces like qa1, qa2, etc., and each has a fleet my-fleet, where 1-2 game servers are launched.
I did debug and saw that ListGameServersByFleetOwner returned all game servers in a cluster with fleet owner name my-fleet.
I'm expecting that fleet and game servers are namespaced resources.
I did the simple fix - we just added namespace name to fleet name, like my-fleet-qa1, my-fleet-qa2
What you expected to happen:
Fleet is the namespaced resource. I need to be able to create a fleet with the same name in different namespaces with CountsAndLists policy.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
): 1.29The text was updated successfully, but these errors were encountered: