Skip to content
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

⚖ Autoscaling Servers #5

Open
nikhiljha opened this issue Jan 3, 2022 · 0 comments
Open

⚖ Autoscaling Servers #5

nikhiljha opened this issue Jan 3, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@nikhiljha
Copy link
Owner

Each game and proxy should report a utilization metric (num players connected / player slots). CRDs should define minReplicas (#), maxReplicas (#), and desiredUtilization (%). If the utilization is below the desired utilization, the replicas should be scaled down (with limit as minReplicas). If the utilization is above the desired utilization, the replicas should be scaled up (with limit as maxReplicas).

To determine which games are ready for scale down, there should be a Java API to set canTerminate (bool). If canTerminate is false, the pods should not be terminated. By default, canTerminate is true, so if no plugin sets it, it will be assumed that the server can be stopped. Scaling up is trivial.

@nikhiljha nikhiljha added the enhancement New feature or request label Jan 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant