You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
The text was updated successfully, but these errors were encountered: