<p>Is it possible to schedule upcoming Pods/Containers based on their priorities?
(if container1 is critical and needs resources, the google orchestrator can kill other low priority containers)
If yes, is there some specific priorities tags (like: critical, monitoring, production...)? </p>

<p>This use case is described in both the <a href="https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/43438.pdf" rel="noreferrer">Borg paper</a> and the <a href="https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/41684.pdf" rel="noreferrer">Omega paper</a>. However, it is not presently implemented within Kubernetes. Here are some related links to ongoing proposals: </p>

<ul>
<li><a href="https://github.com/kubernetes/kubernetes/issues/147" rel="noreferrer">QoS Tiers</a></li>
<li><a href="https://github.com/kubernetes/kubernetes/issues/22212" rel="noreferrer">Preemption Policy / Scheme</a></li>
<li><a href="https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/resource-qos.md#under-development" rel="noreferrer">Resource Quality of Service</a></li>
</ul>
