Thanks a lot for the info! Is there any workaround ideas until 1.8? Like setting up a cronjob which periodically checks for pending guaranteed pods and if there are some kills other QoS pods.
On Wednesday, 2 August 2017 21:56:13 UTC+2, David Oppenheimer wrote: > On Wed, Aug 2, 2017 at 11:44 AM, Rodrigo Campos <rodr...@gmail.com> 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." > > > > On Wednesday, August 2, 2017, <bah...@gmail.com> wrote: > > > Yes, it is about the resources. The guaranteed pods are pending because the > resources are used up. > > What I expect or want to have that the pods that are not guaranteed get > terminated and resources become available when I want to spin up more > guaranteed pods. > > > > -- > > 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. > > > > > > > > > -- > > 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 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.
