On Wednesday, August 2, 2017, 'David Oppenheimer' via Kubernetes user discussion and Q&A <[email protected]> wrote:
> > > On Wed, Aug 2, 2017 at 11:44 AM, Rodrigo Campos <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> The burstable pod must be reserving something also, and that reservation >> (not the limit when there is idle capacity) is making it impossible to >> schedule more pods. >> >> IIRC, burstable or guaranteed is specially relevant when eviction needs >> to be done (node running oom, inode exhaustion, etc.). But it is not >> relevant at all to schedule new pods (again, iirc). >> >> So, I don't think this can help you. Check the docs, just in case, >> anyways :-) >> >> I think some sort of priority (like schedule pods on this namespace >> before pods on some other) was an idea, but don't know what happened to it >> :-) >> > > This is coming, currently scheduled for 1.8. Priority will be used in > deciding "who goes pending and who gets to run when there are more pod > request than cluster capacity" and also "who gets evicted when the node > runs low on resources." > Cool, thanks! How are these features called? Or how can I know more about them? :-) -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
