-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Allow scaling node group to/from 0. #43
Comments
@mwielgus I was wondering if there is a special reason why this is enabled only for GCE and not for AWS or Azure? |
@Shimi However I will happily accept the contributions from the community. It is just a matter of implementing: and Feel invited :). |
cc: @mumoshu @andrewsykim |
Thanks for informing me :) |
@mumoshu We're interested in this feature on AWS, so would be glad to test it on our deployment. |
Closing in favor of #132. |
Automatic merge from submit-queue Add e2e for cluster-autoscaler scale-up from 0 Ref: kubernetes/autoscaler#43
I don't understand if this feature can be activated also on GKE, if i try to set the minimn size to 0 i have the following error:
|
This should work on GKE clusters using kubernetes 1.7. I don't think 1.7 clusters are available right now, but they should be very soon. |
Ok just tried now, master and pool upgraded to 1.7.0:
|
Kubectl version
|
This is an umbrella bug for allowing scaling some node groups to/from 0.
cc: @MaciekPytel @fgrzadkowski
The text was updated successfully, but these errors were encountered: