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

GKE Scheduler #82

Open
hungpv29 opened this issue May 6, 2020 · 1 comment
Open

GKE Scheduler #82

hungpv29 opened this issue May 6, 2020 · 1 comment

Comments

@hungpv29
Copy link

hungpv29 commented May 6, 2020

I have some questions:

  • If Minimum size in the node-pool is >0 the resize action will probably fail

  • If autocscaling is on in the node-pool, I do not know what will happen with the reduction size command

@eranchetz
Copy link
Contributor

@hungpv29 thanks for your questions:

  1. zorya is changing the size of the underlying managed instance group and not the node pool itself, as far as I tested even if the minimum number is >0 it still works.

  2. It is not recommended to use auto-scaling with zorya as it will probably scale the VM back up (it's is managed by GKE Cluster Autoscaler)
    If auto-scaling is a must, I suggest using Kube-Downsclaer it will enable you to downscale your Deployments, StatefulSets, and/or HorizontalPodAutoscalers during non-work hours and then the ClusterAutosclaer will go into effect and scale down the node-pool.

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

2 participants