I'm looking for a way to configure these options
http://kubernetes.io/docs/admin/out-of-resource/ when launching the
kubelet via kops.

On Mon, Jan 2, 2017 at 2:35 AM, Timo Reimann <ttr...@googlemail.com> wrote:

> I'm not familiar with kops but I'd guess you could achieve something
> similar by employing memory resources
> <http://kubernetes.io/docs/user-guide/compute-resources/#how-pods-with-resource-requests-are-scheduled>
>  and
> resource quotas <http://kubernetes.io/docs/admin/resourcequota/> to
> prevent containers from requesting/consuming more memory than a specified
> limit. From my understanding, containers exceeding the resource limit would
> be evicted automatically (subject to the QoS classes they fall into).
>
> (Disclaimer: I haven't used resource constraints to the extent described,
> so I'm mostly interpreting the available documentation in best-effort
> manner.)
>
> HTH.
>
>
> On Sunday, January 1, 2017 at 12:46:53 AM UTC+1, Yervand Aghababyan wrote:
>>
>> for example I want the kubelet to monitor the RAM pressure and stop
>> allocating new pods to the node if the memory usage is above 70%. If it's
>> above 80 I want some of the pods to be moved to other nodes. This seems to
>> be entirely possible to do with some kubelet command line arguments but I
>> don't know how I can customize them if nodeup is starting the
>> cluster(that's what happens if one uses kops, doesn't it?).
>>
>> On Sat, Dec 31, 2016 at 1:42 PM, 'David Oppenheimer' via Kubernetes user
>> discussion and Q&A <kubernet...@googlegroups.com> wrote:
>>
>>> Can you explain what you mean in more detail?
>>>
>>>
>>> On Sat, Dec 31, 2016 at 12:25 AM, <yervand.a...@gmail.com> wrote:
>>>
>>>> Is there a way to specify eviction policies when bringing up a cluster
>>>> using kops?
>>>>
>>>> --
>>>> 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/to
>>> pic/kubernetes-users/YJJ3Cicw8Y0/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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 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.
  • [kubernetes... yervand . aghababyan
    • Re: [k... 'David Oppenheimer' via Kubernetes user discussion and Q&A
      • Re... Yervand Aghababyan
        • ... 'Timo Reimann' via Kubernetes user discussion and Q&A
          • ... Yervand Aghababyan

Reply via email to