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 :-) On Wednesday, August 2, 2017, <[email protected]> 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 [email protected] <javascript:;>. > To post to this group, send email to [email protected] > <javascript:;>. > 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 [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.
