[go: up one dir, main page]

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

Specify min and max. #7

Open
gianarb opened this issue Mar 13, 2017 · 2 comments
Open

Specify min and max. #7

gianarb opened this issue Mar 13, 2017 · 2 comments

Comments

@gianarb
Copy link
Owner
gianarb commented Mar 13, 2017

At the moment our policy just manage up and down but we also need to have some sort of limit related:

  • min how many instances you need to have always up.
  • max is the other side limit. It can be 0 it means infinite.
@plourenco
Copy link
plourenco commented Oct 27, 2017

+1
Is there a milestone for this feature to be implemented?

@dazinator
Copy link

Hi The labels for up and down, wasnt immediately obvious what they meant. After reading the readme it seemed to me at first that they were the desired number of instances that should be running when scaled up or scaled down.. for example if I trigger up multiple times, and the label for up is 2, will I only ever have 2 services running. When I trigger down it goes back to whatever down is. Perhaps my initial interpretationis wrong here. If what actually happens is that it increment by 2 instances each time you apply a scale up then perhaps the label names could be renamed a bit so that up and down labels are more up increment and down increment or something that makes it more obvious!

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

No branches or pull requests

3 participants