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

Better checking of current scale events in progress before scaling up/down #6

Open
naorlivne opened this issue Jan 29, 2020 · 0 comments

Comments

@naorlivne
Copy link
Owner

Expected/Wanted Behavior

If a scaling event is already in progress (was increased/decreased) but the server has not yet fully joined/left the cluster another server shouldn't be added/removed

Actual Behavior

the current scaling events doesn't cover all edge cases so a server might be added while another server is in the process of being added

This can be achieved by comparing the number of servers in the spotinst API to the kubernetes API and if the 2 don't match wait until they do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant