Thanks Beata Skiba,

Will this means, that all the users pods created by either stateful-set or
replica-set, will be scheduled to the one node, that is used for system
pods ?

I was thinking that, if i made node-pool =0, it will down everything. We
have auto-scaling enabled in our clusters.

Thanks Again!



On Thu, Aug 17, 2017 at 2:59 PM, 'Beata Skiba' via Kubernetes user
discussion and Q&A <kubernetes-users@googlegroups.com> wrote:

> With autoscaling enabled for your cluster you can scale down a certain
> node pool to 0 (beginning with Kubernetes version 1.7), but not the whole
> cluster (there will always be at least one node needed) since there are
> system pods that need to be scheduled.
> See: https://cloud.google.com/container-engine/docs/cluster-
> autoscaler#minimum_and_maximum_node_pool_size
>
> This can work for your use case if you can accept a one node cluster
> working overnight.
>
> On Wednesday, August 16, 2017 at 2:05:25 PM UTC+2, Matthias Rampke wrote:
>>
>> Does GKE let you scale the cluster to 0 nodes? I'm not very familiar with
>> GKE in particular but since it manages the size of the cluster (and
>> replacing lost nodes) I think you just need to tell it what you want
>> instead of going behind it's back.
>>
>> /MR
>>
>> On Wed, Aug 16, 2017 at 11:42 AM <sup...@bitpod.io> wrote:
>>
>>> hello,
>>>
>>> I have created a container engine cluster with 5 nodes, using
>>> n1-standard-8 machine type. The machine is generally for development
>>> purpose.
>>>
>>> Is there any way, in which i can make my clusters down(sleep mode)
>>> during night time. And start them in the morning ?
>>>
>>> I have tried by stopping the VM's associated with the cluster, but as
>>> soon i stopped it, it will re-create it.
>>>
>>> Conditions :
>>>
>>> 1. I have a lot of pods, which should not affect, when i restart the
>>> cluster next day.
>>>
>>> 2. Also, some pv's are associated with the pods.
>>>
>>>
>>> Any help will be appreciated!
>>>
>>> Thanks.
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Kubernetes user discussion and Q&A" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to kubernetes-use...@googlegroups.com.
>>> To post to this group, send email to kubernet...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/kubernetes-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Kubernetes user discussion and Q&A" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/kubernetes-users/OyrebZC7yTo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to